Integration

Enterpryze to
Mintsoft

Enterpryze runs your sales orders, inventory and invoicing. 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.

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
Enterpryze 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 DESPATCHED
Enterpryze 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 Enterpryze 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.

  • Enterpryze 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 Enterpryze
  • Fulfilment status on the sales order updated automatically
  • Stock movements in Mintsoft reflected back to Enterpryze
  • Order hold and release logic supported
  • Multi-warehouse routing across Mintsoft warehouse accounts
Integration flow summary
Enterpryze 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
DESPATCHED
Enterpryze 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 Enterpryze automatically: stock receipted and the 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 Enterpryze 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 Enterpryze 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.

1

Order trigger

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

2

SKU and product mapping

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

3

Carrier and service mapping

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

4

Tracking and status writeback

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

Carrier service mapping example
Enterpryze 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
ON
Tracking writeback
On despatch event
ON
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 Enterpryze 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, so 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 Enterpryze."

Partial despatch events are handled individually. Each shipment from Mintsoft creates its own tracking record against the Enterpryze 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.

"Mintsoft has updated its carrier service names and our orders are now routing incorrectly."

Carrier and service code mappings are maintained in Supply Lens, not hardcoded anywhere. When Mintsoft changes a service name, one update at the mapping layer fixes it across every order without touching either system.

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.

  • Enterpryze API credentials and account details
  • Mintsoft API credentials and warehouse name(s)
  • List of carrier services used in Mintsoft
  • Enterpryze shipping method names to map against
  • Fulfilment trigger status in Enterpryze
  • Sample sales orders (5–10 representative examples)
  • Any SKU differences between Enterpryze and Mintsoft
  • Warehouse routing rules if using multiple locations
  • Returns and stock sync requirements (if needed)
Typical delivery timeline
1
Scope
API credentials, carrier mapping, warehouse names and sample orders received.
2
Configure
SKU mapping, carrier services, trigger rules and writeback fields built in staging.
3
Test
Test orders through Mintsoft, despatch and tracking confirmed back in Enterpryze.
Go live
Production enabled, monitoring active, first live order through in minutes.

Ready to connect
Enterpryze and Mintsoft?

Most customers are live within 1–2 days. No long contracts. No warehouse downtime.