Connect Mintsoft to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Mintsoft and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Mintsoft EDI
XEDI connects Mintsoft with retailer and carrier EDI so orders arrive against the right client and warehouse, and despatch confirmations, ASNs and invoices go back out carrying the pack detail each retailer expects.
One managed platform, no custom code
XEDI maps Mintsoft to your trading partners and validates every document, so data flows straight into the systems your teams already use.
With a 3PL, the first question is whose trading relationship it is
Mintsoft is usually running more than one brand in the same building. So when a retailer sends an order, it is not simply an order for you: it is an order for one of your clients, and it has to land against their stock, their SKUs and their account.
Getting that wrong is not a formatting problem, it is a stock problem. An order allocated against the wrong client consumes inventory that belongs to somebody else, and by the time anyone notices it has usually shipped.
Pack detail is what the retailer's goods-in actually reads
A retailer's receiving bay does not read your despatch note. It scans a label and expects to find a hierarchy behind it: this pallet contains these cartons, which contain these units of this product. If that structure does not match what physically arrives, the delivery is disputed at the door.
So the despatch advice is built from what Mintsoft actually picked and packed rather than from what was ordered, with SSCC labels for the pallets. Where you have shipped short or substituted, the document says so before the lorry arrives rather than after.
What your warehouse sees day to day
You get an EDI mailbox and a portal that works like an inbox. Retailer orders arrive against the right client, your team is notified, and work can start before the Mintsoft integration is finished.
The order then becomes the despatch advice from what was actually picked, amended where you are sending more or less than ordered, with SSCC labels for the pallets, and becomes the invoice on delivery, whose arrival is confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders drop into Mintsoft and fulfilment raises the outbound documents. Smaller operators run the portal alone; our API suits enterprises needing finer granularity; a multi-client warehouse normally wants the integration.
Documents you can exchange
- Retailer orders landing against the right Mintsoft client and warehouse
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages raised from Mintsoft fulfilment
- Goods-in and receiving advice against expected stock
- Invoices, or fulfilment charges where you are the 3PL
Built for Mintsoft teams
Whoever owns Mintsoft in your business, XEDI keeps EDI accurate and hands-off.
- Third party logistics operators
- Ecommerce and wholesale fulfilment teams
- Warehouse managers running multiple clients
- Client services teams onboarding brands
- Finance teams billing fulfilment activity
Mintsoft EDI document types
Which of these apply depends on whether you are fulfilling for clients or trading in your own right.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a Mintsoft order against the correct client, SKUs and warehouse. | Retailer to Mintsoft |
| Order acknowledgements | What will actually be fulfilled once stock is allocated against that client's holding. | Mintsoft to retailer |
| Advanced shipping notices | Pallet and carton hierarchy built from what was picked, carrying the SSCC labels the retailer's goods-in scans. | Mintsoft to retailer |
| Receiving advice | Confirmation of what arrived against an expected delivery, so a client's stock position reflects reality. | Either direction |
| Invoices | Raised where you trade in your own right, referenced to the despatch. | Mintsoft to retailer |
| Stock reports | Holdings by client and location where a retailer plans replenishment against your figures. | Mintsoft to retailer |
How to connect Mintsoft with EDI using XEDI
A Mintsoft build is mostly about routing: which client, which warehouse, which courier. The sequence below is what onboarding looks like from your side.
-
01
We scope which Mintsoft clients, warehouses and carriers each retailer relationship runs through.
-
02
We build the mapping between each retailer's documents and your Mintsoft clients, SKUs, locations and courier services.
-
03
We configure validation so an order is checked against the retailer's rules before it becomes a Mintsoft order.
-
04
We prove the order, despatch and goods-in flows against what each retailer requires and against how your warehouses are set up.
-
05
You get orders landing against the right client every time, and we keep it that way as you take on new ones.
Ready to connect Mintsoft?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Mintsoft EDI
Common requirements
- Mintsoft account and API access
- Client, warehouse and courier structure
- SKU and packaging data per client
- Goods-in and expected stock rules
- The trading partners you deal with, or plan to
What we need from you to build it
Only what we cannot hold for you. Retailer requirements are already ours; what we need is how your warehouse and clients are arranged.
- Mintsoft access
- API credentials with rights to the orders, stock and despatch endpoints across the clients in scope.
- Client and warehouse structure
- Which client each retailer relationship belongs to, and which warehouse services it, since allocation follows that.
- SKU and packaging data
- Each client's SKUs against the identifiers retailers send, with units per carton and cartons per pallet.
- Courier and service mapping
- Which courier service each retailer or delivery type uses, so the despatch advice carries the right tracking detail.
- Which retailers are in scope
- The relationships to connect, and for which client. What each retailer requires is already ours.
Why suppliers choose XEDI for Mintsoft
- The retailers your clients supply are generally connected already, so onboarding a brand does not start with a connectivity project.
- Orders are allocated against the correct client before they reach Mintsoft, so one brand's stock is not consumed by another's order.
- The despatch advice is built from what was picked rather than what was ordered, which is what stops a delivery being disputed at goods-in.
- Onboarding a client's retailer is our work, so taking on a brand does not mean a fulfilment project.
- SSCC labels and pallet hierarchy are produced to each retailer's format rather than a generic one.
- If a retailer raises a problem it comes to us. We are notified on your behalf and fix it before your client hears about it.
Can XEDI handle multiple clients in one Mintsoft account?
Yes, and it is normally the reason for using it. Each retailer relationship is mapped to the client and warehouse it belongs to, so orders allocate against the right stock rather than the right-looking stock.
Who does the retailer deal with, us or our client?
That is settled at scoping and reflected in how documents are addressed and identified. Either way we hold the retailer's requirements, so nobody in your team is interpreting a specification.
Can it produce the pallet labels retailers scan?
Yes. SSCC labels and the pallet-to-carton hierarchy are generated from what Mintsoft actually picked, in the format each retailer's goods-in expects.
Plan your Mintsoft EDI setup
Everything you need to scope, map and go live with Mintsoft, in one place.