Does the integration work with both Cin7 Core and Cin7 Omni?

Yes. Supply Lens connects both Cin7 Core (formerly DEAR) and Cin7 Omni to Mintsoft. The order handoff, despatch and tracking writeback flows are the same; only the API credentials differ between the two products.

How quickly can Cin7 be connected to Mintsoft?

Most Cin7 to Mintsoft connections are live within one to two working days once API credentials, carrier service mappings and warehouse names have been provided.

What happens if a Cin7 product code does not match the Mintsoft SKU?

Unrecognised SKUs are caught before the order is submitted to Mintsoft. The order is held in an exception queue with a clear notification, so the warehouse never receives an order it cannot process and nothing is silently dropped.

Integration

Cin7 to
Mintsoft

Cin7 manages your inventory and orders. Mintsoft runs your warehouse. Supply Lens connects them: orders hand off automatically, the warehouse despatches and tracking comes back without anyone touching it in between. Fast to configure, fast to go live.

Works with Cin7 Core Works with Cin7 Omni

Talk to the team Start free trial →

15min

Order handoff lag

Mintsoft is polling-based rather than webhook-driven

4flows

Core sync flows

99.9%

Uptime SLA

Supply Lens — Live Flow Monitor Live

Cin7 SO-11432 ready to fulfil 3× Brushed Cotton Hoodie, 1× Beanie: £184.00 ORDER READY

Validated & transformed SKUs mapped · service DPD-NEXT · warehouse UK-MAIN PROCESSING

Mintsoft WO-84221 created Warehouse order accepted · pick in progress WO CREATED

Despatched by Mintsoft DPD 15082719001GB · tracking received DISPATCHED

Cin7 SO-11432 fulfilled Despatch date set · tracking ref stored · stock decremented SYNCED BACK

Core Capabilities

The warehouse gets
the order. You get
the tracking.

Supply Lens sits between Cin7 and Mintsoft, picking up orders when they're ready to fulfil, sending them to the warehouse and writing everything that comes back into the right place automatically. The same flow works whether you run Cin7 Core or Cin7 Omni.

Cin7 sales orders handed off to Mintsoft when ready to fulfil
SKU and product codes mapped between systems
Carrier service codes translated to Mintsoft shipping service names
Warehouse location routing configured per order or product type
Despatch confirmation and tracking written back to Cin7
Fulfilment status on the sales order updated automatically
Stock movements in Mintsoft reflected back to Cin7
Order hold and release logic supported
Multi-warehouse routing across Mintsoft warehouse accounts

Integration flow summary

Cin7 order ready

Fulfilment status trigger

TRIGGER

Supply Lens validates

SKUs, service, warehouse routing

TRANSFORM

Mintsoft warehouse order

Created, pick & pack begins

CREATED

Despatch + tracking received

From Mintsoft on ship

DISPATCHED

Cin7 updated

SO fulfilled · tracking stored

SYNCED BACK

Optional Flows

More than order handoff.

The core flow is order out and tracking back. But Supply Lens can extend the connection deeper into your warehouse and inventory operations.

Returns & Receipt

Returns handling is often an afterthought in 3PL integrations. Supply Lens writes Mintsoft return events back to Cin7 automatically: stock receipted, sales order or return record updated when goods arrive at the warehouse. No manual import required.

Stock Sync from Mintsoft

Warehouse stock levels in Mintsoft pushed back to Cin7 on a schedule or trigger, keeping your inventory accurate without manual stock counts or imports.

Multi-Warehouse Routing

Route orders to different Mintsoft warehouse accounts based on product type, order tag, customer group or geography, all within the same integration.

Order Hold & Release

Hold orders from passing to Mintsoft until a manual review or approval step is completed. Useful for high-value orders, new customers or flagged accounts.

Partial Fulfilment

Orders partially despatched by Mintsoft, whether multiple shipments, split lines or staged despatch, are handled cleanly with correct status and tracking for each shipment.

Product & SKU Sync

Push new products and SKU updates from Cin7 into Mintsoft, keeping warehouse product records aligned when your catalogue changes.

Configuration

Set up once.
Works every order.

Every Mintsoft account has its own warehouse names, service codes and product identifiers. Supply Lens maps these precisely, so orders arrive at the warehouse already in the format it expects.

Order trigger

Choose when orders hand off: on a specific Cin7 fulfilment status, on despatch instruction or on a scheduled polling interval.

SKU and product mapping

Cin7 product codes mapped to Mintsoft SKUs. Any differences in naming convention are resolved at the Supply Lens layer, not manually at the warehouse.

Carrier and service mapping

Cin7 shipping methods translated to the correct Mintsoft carrier service codes: DPD Next Day, Royal Mail 48, Evri Standard or whichever services your 3PL uses.

Tracking and status writeback

Despatch events and tracking numbers from Mintsoft written back to the correct Cin7 sales order, with configurable fulfilment status and reference field mapping.

Carrier service mapping example

Cin7 method Mintsoft service

DPD-NEXT → DPD Next Day

RM-48 → Royal Mail 48

EVRI-STD → Evri Standard

DPD-SAT → DPD Saturday

Order handoff

On fulfilment status

Tracking writeback

On despatch event

Stock sync

Not enabled

OFF

Returns

Not enabled

OFF

Warehouse

UK-MAIN default

CONFIG

Order hold

Disabled

CONFIG

Edge Cases Handled

3PLs are rarely
straightforward.

Warehouse integrations break on the details. Supply Lens handles the edge cases before they become problems.

"A product code in Cin7 doesn't match the SKU Mintsoft has on file."

Unrecognised SKUs are caught before the order is submitted to Mintsoft. The order goes to an exception queue with a clear notification: the warehouse never receives an order it can't process. Nothing is silently dropped.

"Mintsoft despatches an order in two separate shipments: we need both tracking numbers in Cin7."

Partial despatch events are handled individually. Each shipment from Mintsoft creates its own tracking record against the Cin7 sales order. Both arrive, neither is lost or overwritten by the other.

"We want some orders to go to a different Mintsoft warehouse based on the product category."

Warehouse routing rules are applied per order at the Supply Lens layer, by product tag, customer group, shipping zone or order value. Mixed orders with lines for different warehouses can be split and routed accordingly.

"We're on Cin7 Omni now but may move to Cin7 Core: will the integration still work?"

The Mintsoft connection is built at the Supply Lens layer, not hardwired to one Cin7 product. Both Cin7 Core and Cin7 Omni are supported, so a move between them is a credential and mapping change, not a rebuild.

What you'll need

Live in two days,
typically.

Supply Lens handles the connection and mapping. You provide API access to both systems and confirm the carrier services, warehouse names and fulfilment trigger rules.