|
Current Problem
Many Mintsoft users integrate with external fulfilment systems like Go2Stream for automated order processing and despatch. Currently, Mintsoft’s label output doesn’t include the barcode data Go2Stream (and similar platforms) need to scan shipments directly from the Mintsoft-generated labels. Go2Stream have already confirmed what’s required for compatibility, Mintsoft would just need to include a Code 128 or QR code on the label, with the value. This data is already available in Mintsoft’s API responses, so implementation should be straightforward. Adding this would mean users can generate Go2Stream-ready labels directly within Mintsoft, avoiding separate label downloads and improving overall fulfilment speed. This isn’t only useful for Go2Stream, the same enhancement would benefit any user working with scanning-based 3PL or retailer systems that need barcode-encoded shipment data. A small change that could make a big difference across the Mintsoft community, please vote if you’d like to see better compatibility with external fulfilment partners! |
|
| Idea to resolve Problem | Allow custom label templates to be defined and applied per courier or integration, so that labels generated within Mintsoft can include the specific fields, barcode formats, or layout required by each fulfilment partner (e.g., Go2Stream, EDI retailers, or 3PL systems). This would make it possible for users to generate fully compliant labels directly from Mintsoft without needing to download them separately from other portals, improving integration flexibility and workflow efficiency across all shipping channels. |