Connect ProSKU to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between ProSKU and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with ProSKU EDI
XEDI connects ProSKU with retailer EDI so orders arrive against the right client and stock, and despatch confirmations go back carrying the pallet detail and labels retailers require at goods-in.
One managed platform, no custom code
XEDI maps ProSKU to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Smaller operations feel a retailer's requirements hardest
A large distribution business absorbs the cost of a retailer's compliance rules across a lot of volume. A smaller warehouse running ProSKU does not have that cushion, and a single deduction for an unreadable pallet label or a late despatch confirmation is a meaningful number.
That is the case for not writing those rules yourself. The requirements are detailed, they change without much notice, and getting them wrong costs more proportionally the smaller you are.
Client separation matters even at modest volume
ProSKU sites usually hold stock for more than one client. An order has to be allocated against the right one, and a receipt has to increase the right one's holding, or your stock records diverge from what you are contractually holding for somebody.
The mapping decides that before anything reaches the warehouse floor, rather than relying on whoever is processing the order recognising which brand it belongs to.
What your warehouse sees day to day
You get an EDI mailbox and a portal that works like an inbox, so retailer orders arrive in one place rather than as emails to an address somebody checks.
What was picked becomes the despatch advice, adjusted where the quantities moved, with SSCC labels applied at pallet level, and the invoice follows delivery with its arrival confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders drop into ProSKU and despatch raises the outbound documents. Many smaller operators run the portal alone and add the integration when volume justifies it; our API is there for finer requirements again.
Documents you can exchange
- Retailer orders landing as ProSKU orders
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages from ProSKU despatch
- Goods-in confirmation against expected deliveries
- Stock reports by client where required
Built for ProSKU teams
Whoever owns ProSKU in your business, XEDI keeps EDI accurate and hands-off.
- Smaller third party logistics operators
- Warehouse managers
- Client services teams
- Goods-in and despatch teams
- Businesses moving off spreadsheets for fulfilment
ProSKU EDI document types
Which apply depends on whether you fulfil for clients or trade in your own right.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a ProSKU order against the correct client, SKUs and location. | Retailer to ProSKU |
| Order acknowledgements | What will be fulfilled from that client's holding, including short lines. | ProSKU to retailer |
| Advanced shipping notices | Pallet and carton structure from the despatch, with SSCC labels the retailer's goods-in scans. | ProSKU to retailer |
| Receiving advice | What arrived against what was expected, so a client's holding reflects reality. | Either direction |
| Stock reports | Holdings by client where a retailer or client plans against your figures. | ProSKU to recipient |
| Invoices | Raised where you trade in your own right rather than fulfilling for a client. | ProSKU to retailer |
How to connect ProSKU with EDI using XEDI
The build is mostly about client allocation and label compliance. The sequence below is what onboarding looks like from your side.
-
01
We scope which ProSKU clients and stock each retailer relationship draws on.
-
02
We build the mapping between each retailer's documents and your ProSKU clients, SKUs and locations.
-
03
We configure validation so an order is checked against the retailer's rules before it reaches the warehouse.
-
04
We prove the order, despatch and goods-in flows against what each retailer requires and against how your operation runs.
-
05
You get orders arriving against the right client, and we keep it correct as you take on new ones.
Ready to connect ProSKU?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about ProSKU EDI
Common requirements
- ProSKU account and integration access
- Client and location structure
- SKU and pack data per client
- Goods-in and expected delivery 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, including label formats, are already ours.
- ProSKU access
- Integration credentials with rights to the order, stock and despatch functions across the clients in scope.
- Client structure
- Which client each retailer relationship belongs to, since allocation and stock movements follow it.
- SKU and pack data
- Each client's SKUs against retailer identifiers, with units per carton and cartons per pallet.
- Goods-in expectations
- How inbound deliveries are booked and received, so a receipt can be checked against something.
- 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 ProSKU
- The retailers involved are typically connected already, so a small operator is not funding a connectivity build.
- Retailer compliance rules are held and maintained by us, which matters most when a single deduction is a meaningful number.
- Orders allocate against the right client before reaching the warehouse floor, rather than relying on recognition.
- SSCC labels are produced to each retailer's format from the actual despatch.
- You can start on the portal alone and add the integration when volume justifies it, without changing anything the retailer sees.
- If a retailer raises a problem it comes to us, and we resolve it before your client is involved.
Is EDI worth it at our volume?
Many smaller operators start on the portal alone, which needs no integration and no development. The ProSKU integration is added when the volume of re-keying justifies it, and that change is on our side rather than yours.
Can you keep clients' stock separate?
Yes. Each retailer relationship is mapped to the client it belongs to, so orders allocate and receipts credit against the correct holding rather than a similar-looking one.
Do retailers require pallet labels from us?
Most do, and the format differs between them. Those requirements are already held by us and labels are generated from what was actually despatched.
Plan your ProSKU EDI setup
Everything you need to scope, map and go live with ProSKU, in one place.