NetSuite owns the order and the ledger. Mintsoft runs the warehouse. Supply Lens connects them. Orders hand off when they are ready to fulfil, the warehouse picks and despatches, then the item fulfilment lands back in NetSuite with tracking, without anyone touching it in between.
Supply Lens sits between NetSuite and Mintsoft, picking up sales orders when they are ready to fulfil, sending them to the warehouse and writing everything that comes back into the right NetSuite record automatically.
The core flow is order out and fulfilment back. Supply Lens can extend the connection deeper into your warehouse and inventory operations.
Every Mintsoft account has its own warehouse names, service codes and product identifiers. Every NetSuite account has its own locations and ship methods. Supply Lens maps between them precisely, so orders arrive at the warehouse in the format it expects.
Choose when orders hand off: on pending fulfilment status, on a custom field or saved search, or on a scheduled polling interval.
NetSuite item names or internal IDs mapped to Mintsoft SKUs. Differences in naming convention are resolved at the Supply Lens layer rather than manually at the warehouse.
NetSuite ship methods translated to Mintsoft carrier services, and NetSuite locations to Mintsoft warehouses, so each order goes to the right building with the right service.
Despatch events from Mintsoft create item fulfilments against the correct NetSuite sales order, with configurable status, tracking field and location.
Warehouse integrations break on the details. These are the four we hear about most, in the words customers use.
Unrecognised SKUs are caught before the order is submitted. The order goes to an exception queue with a clear notification, so the warehouse never receives an order it cannot process. Nothing is silently dropped.
Each shipment creates its own item fulfilment against the sales order, with its own tracking and quantities. NetSuite shows both. The order closes when the last one lands and neither overwrites the other.
Location to warehouse mapping is applied per order, or per line where a mixed order needs splitting. Subsidiary, item class and customer can all drive the route as well.
Ship method and service mappings live in Supply Lens rather than being hardcoded anywhere. When Mintsoft changes a service name, one update at the mapping layer fixes it across every order without touching either system.
Supply Lens handles the connection and mapping. You provide access to both systems and confirm the carrier services, warehouse names and fulfilment trigger rules. Agreeing which NetSuite location each warehouse represents is what takes the time.
Tell us which NetSuite locations your warehouses represent and which carriers you run. Twenty minutes is usually enough to size the work.