We build and run it for you.
Your partners' documents, as NetSuite records.
A purchase order arrives and becomes a sales order. The acknowledgment goes back. The ship notice is built from the fulfilment, and the invoice follows it. Each document is validated against the schema we hold for that partner before anything is created in your account.
We do the mapping and we watch the queue. A document that fails validation is held whole and raised as an exception, so nobody gets a half-built sales order to unpick.
Each partner is configured as an accessor with its own identifier and credentials. Tell us who you trade with and we'll tell you what's involved.
This is the same partners summary and documents table your team sees in the app. The status dot follows one rule: only dispatched is success, validated and standardised are progress, the awaiting states are warnings, and denied or orphaned are errors.
The four documents, and the order behind them
The app names them the way your partners' guides do, and each one has a viewer that shows you the document as we understood it rather than only the raw segments. If a partner needs a type that isn't here, ask. Adding one is work, but it isn't research.
Purchase order
Inbound. Becomes a sales order, with item cross-reference and price checks before it lands.
Acknowledgment
Outbound. Accepted, backordered or rejected, line by line.
Ship notice
Outbound, built from the fulfilment rather than typed again.
Invoice
Outbound, reconciled against what they acknowledged.
The order's own progress
Underneath the documents, each order moves through five stages. This is the app's own component, so what you see here is what your team sees on the order.
Partial states are real states: partially shipped and partially invoiced both exist, and so does exception, which is where an order sits when a document was held.
What happens when a document is wrong
Partners send malformed documents. Items get renamed on their side and not yours. Prices disagree by five cents. This is most of the actual work, and it decides whether EDI is quiet or a daily chore.
A document that fails validation is held in one piece and raised as an exception. Nobody gets a partial sales order to unpick. There's a review screen for the held ones, so the person fixing a cross-reference can see the document, fix the mapping and reprocess it in the same place.
The statuses are deliberately specific about this. Validated and standardised mean progress, not success. Awaiting review, awaiting correction and awaiting document are three different problems. Orphaned and denied are two more. Only dispatched means it left.
Before you talk to us
Get the partner's implementation guide. Everything we can tell you depends on it, and asking them for it is the slowest step.
Know whether your item codes match theirs. If they don't, someone has to build the cross-reference, and that someone knows your products better than we do.
If you have one partner and four orders a week, EDI is probably not worth it yet. We'll say so.
Send us the implementation guide.
We'll read it and tell you what it takes, which parts of it are unusual, and where your item codes are going to cause trouble. Including when the answer is that you don't need us.
The other four
Labels
Carton and product labels off the sales order. Free to 250 a month.
Freight
Live rates from every carrier account you hold, then book and print.
Power BI
Scheduled pipelines out of NetSuite into storage Power BI can read.
3CX
The customer's record and their open orders while the phone is ringing.
Direct Print
Push print jobs directly to your registered DataShift print devices.