On your way to joining us?
Let us show you what we do.
This page gives you a quick look at who we are and the core concept behind almost everything we build: EDI, or Electronic Data Interchange. It's the language businesses use to talk to each other automatically, and understanding it is your starting point for this role.
🔗 www.truecommerce.comTrueCommerce connects businesses, ERP systems, and trading partners on a single network, powered by EDI, APIs, and increasingly AI. Instead of every company building its own connection to every partner, TrueCommerce maintains one platform that already speaks the language of over 180,000 retailers, distributors, and logistics providers, including names like Amazon, Tesco, and Unilever.
Receive and process purchase orders automatically.
Send and reconcile invoices without re-keying data.
Send an Advance Shipping Notice (ASN), a heads-up telling the buyer what is being shipped and when, so they can plan ahead.
Sync stock across ERPs and online marketplaces.
Whether you're heading into implementation, support, integration, or customer success, EDI is the language you'll hear in almost every conversation with a customer or trading partner. Keep scrolling. The next section breaks it down with a real example, so you can walk in already speaking it.
Electronic Data Interchange (EDI) is the automated exchange of business documents, like purchase orders, invoices, and shipping notices, directly between two companies' computer systems, in a standard format, with no manual re-typing.
Takes a document out of one company's system, converts it into the standard format the other side expects, delivers it securely, and confirms it arrived.
Without the platform in the middle, every company would need to build and maintain a separate connection to every partner it trades with.
Buyer places the order electronically
Supplier confirms what is shipping, when, and how to track it
Supplier sends the billing document
Buyer confirms the messages were valid
Saying "EDI 850 equals a purchase order" only goes so far, so here is one actual order, shown two ways. Nothing is added or removed between the two, it's the same information.
Read the left side first. That's the most familiar format for almost all of us in daily life. The right side is simply what that same order looks like once it has been translated into EDI inside the system, good to recognize, not something you need to memorize.
| # | Item | Qty | Unit price |
|---|---|---|---|
| 1 | Blue cotton t-shirt, size M UPC 012345678905 | 120 cases | $18.50 |
| 2 | Blue cotton t-shirt, size L UPC 012345678912 | 60 cases | $22.00 |
ISA*00* *00* *ZZ*ACMERETAIL *ZZ*BRIGHTAPPAREL *260817*1030*U*00401*000000905*0*P*>~ GS*PO*ACMERETAIL*BRIGHTAPPAREL*20260817*1030*1*X*004010~ ST*850*0001~ BEG*00*SA*PO-4417**20260817~ DTM*002*20260901~ N1*ST*ACME RETAIL DC 12*92*0012~ N3*45 HARBOR ROAD~ N4*DALLAS*TX*75201*US~ PO1*1*120*CA*18.50**UP*012345678905~ PID*F****BLUE COTTON T-SHIRT, SIZE M~ PO1*2*60*CA*22.00**UP*012345678912~ PID*F****BLUE COTTON T-SHIRT, SIZE L~ CTT*2~ SE*12*0001~ GE*1*1~ IEA*1*000000905~
Each line is a segment. The first code says what the line is for, and the asterisks separate the data elements. The tilde marks the end of the line.
| Segment | Raw | What it means in plain English |
|---|---|---|
| ISA / GS | ISA*00*...*ZZ*ACMERETAIL | The envelope. Who sent it, who receives it, when, and which version of the standard is used. |
| ST | ST*850*0001 | Start of the document. This one is a 850, meaning a purchase order. |
| BEG | BEG*00*SA*PO-4417**20260817 | Order header: a new standalone order, number PO-4417, dated 17 Aug 2026. |
| DTM | DTM*002*20260901 | A date. Code 002 means requested delivery date, so 1 Sep 2026. |
| N1 / N3 / N4 | N1*ST*ACME RETAIL DC 12 | A party and its address. ST means ship to, so this is the delivery location. |
| PO1 | PO1*1*120*CA*18.50**UP*012345678905 | Order line 1: 120 cases at $18.50 each, identified by UPC 012345678905. |
| PID | PID*F****BLUE COTTON T-SHIRT, SIZE M | A plain text description of the item on the line above. |
| CTT / SE | CTT*2 · SE*12*0001 | Control totals. Two line items, 12 segments in the document. The receiver uses these to confirm nothing was lost in transit. |
This sample is simplified for illustration. Real trading partner files carry more segments, and every retailer has its own specific requirements, which is a large part of what our teams manage day to day.
Orders, invoices, and shipping updates move in seconds instead of days of manual handling.
No manual re-keying means far fewer data entry errors and costly mismatches.
Both sides can track exactly where a transaction stands, with automated acknowledgments.
These teams work on different parts of the platform, each with its own focus. Broadly, some get a customer up and running, and others keep everything running once they're live.
You guide a new customer through getting set up, translating what their business needs into a working configuration.
You build and configure the technical mapping behind a connection, matching each trading partner's exact requirements.
When a transaction fails or data stops flowing, you investigate what went wrong and get it moving again.
The voice trading partners hear day to day, handling their questions and issues on their side of the connection.
Job titles vary between platforms, regions, and teams, so the role you applied for may sit across more than one of these. Your recruiter can walk you through where it fits.
See what we're hiring for right now.
Browse open roles →