Five integrated data flows. Orders in, purchase orders as ASNs, receipts out, stock updates out, shipments out. Supply Lens connects Mintsoft to your ERP, storefronts and finance systems with every courier, channel, SKU, bundle and warehouse configuration handled correctly.
Each flow has its own logic, timing, and edge cases. Supply Lens handles all five, including the configuration decisions that make each one work correctly in practice.
Orders flow from your ERP or storefront into Mintsoft as fulfilment instructions, and Mintsoft order status events flow back to keep source systems in sync. Whether the source is Shopify, Unleashed, an EDI trading partner, or any other connected system, Supply Lens transforms the order into the correct Mintsoft format, with the right channel mapping, warehouse assignment and SKU resolution applied at the point of transmission.
When a purchase order is raised in your ERP (whether it's a supplier delivery, an intercompany transfer or an inbound from a retailer) Supply Lens transforms it into an Advanced Shipment Notice (ASN) and sends it to Mintsoft ahead of the physical goods arriving. Mintsoft can then prepare for the inbound, pre-allocate racking, and confirm receipt against the expected quantities. SKU mapping, supplier references and expected arrival dates are all carried through correctly.
When goods are received and confirmed in Mintsoft (whether against an ASN or as an unplanned receipt) Supply Lens captures the Goods Received Note and creates the corresponding receipt in your ERP. Stock levels in the ERP update immediately, purchase orders are marked as received against the ordered quantity and any discrepancies between the expected and received quantities are recorded against the original PO for reconciliation. This closes the loop between what was ordered, what arrived and what is now available.
Mintsoft is the physical source of truth for available stock. Supply Lens takes stock position updates from Mintsoft and pushes accurate available-to-sell quantities to your ERP, Shopify or any other connected channel. Warehouse-level positions are mapped to the correct ERP location or channel availability rules. Where you operate multiple warehouses in Mintsoft, each warehouse's stock is handled independently and routed to the correct downstream system.
When Mintsoft confirms a shipment (picking complete, carrier collected, consignment created) Supply Lens captures the despatch event and pushes it to all connected downstream systems. The ERP sales order is marked as shipped. The Shopify fulfilment is created with the carrier and tracking number. The customer notification fires. Where an order is partially despatched, each shipment event is recorded separately against the open order, keeping the remaining balance accurate. Courier service codes from Mintsoft are translated to the correct labels expected by each downstream system.
Getting Mintsoft connected at an API level is the easy part. Getting it working correctly for your operation requires a configuration layer that knows how your couriers, channels, SKUs, bundles and warehouses relate to each other. That's what Supply Lens handles.
The most common Mintsoft integration pairings. Each pairing uses the same five-flow architecture with configuration tailored to the specific systems involved.
Mintsoft has a well-structured API. The complexity is in the configuration decisions, not the connection itself. These are the scenarios that require an integration layer that understands the operational context.
Supply Lens handles bundle explosion at the integration layer. When an order containing a bundle SKU is sent to Mintsoft, it is automatically expanded into its component parts with the correct quantities. Mintsoft picks the components. The Shopify fulfilment is created against the original bundle SKU. Stock updates return at component level, keeping your ERP position accurate.
Every courier service Mintsoft uses is mapped to the label expected by each downstream system. Royal Mail 48 in Mintsoft becomes RM48 in your ERP and "Royal Mail" in Shopify's carrier field. Tracking URLs are generated correctly because the carrier is identified correctly. This mapping is maintained as part of the ongoing service: when you add a new courier, it's added to the map.
Warehouse routing rules are configured at the integration layer, not assumed. You define which order types, channels or product categories route to each Mintsoft warehouse. Rules can be based on channel, product group, order value, delivery postcode region or any combination. Stock updates return from each warehouse separately and land in the correct ERP location.
The receipt flow closes this gap. When goods are confirmed as received in Mintsoft, Supply Lens creates the corresponding GRN in your ERP and updates stock immediately. Purchase orders are matched and marked fulfilled to the received quantity. Discrepancies between expected and received quantities are recorded against the original PO so nothing is lost in the gap between the physical warehouse and your system.
Most Mintsoft integration projects follow a structured path. You give us what we need, we configure the five flows and the configuration layer, test end-to-end and go live.
Ongoing support includes courier mapping updates, SKU mapping maintenance and warehouse rule changes as your operation evolves.
Five flows, fully configured. Orders, ASNs, receipts, stock and shipments, all automated. 30-day trial available.