Guided product tour · 3 steps

Follow an order from X12 to usable data.

A retailer sends a purchase order. Your order system needs its data. Follow one value through the map, then see which records help you check processing.

Synthetic example · No signup · No documents are sent

1 · The incoming order

Start with the order your partner sends.

The retailer’s X12 850 contains purchase order PO0001. In a connected workspace, hosted AS2 receives the document and the partner’s incoming map determines the data your application gets.

For this example, we’ll extract just the purchase-order number so your system can identify the order.

Sample purchase order

Order number: PO0001
Order date: April 13, 2026
Line item: ITEM-1 · 1 each

See the X12 excerpt

The highlighted value is the order number in the BEG header segment.

ST*850*0001~
BEG*00*SA*PO0001**20260413~
PO1*1*1*EA*100**VN*ITEM-1~

This excerpt omits the envelope and closing segments. The sample case includes the full input and expected output.

Next: read the mapped result

2 · The mapped data

Give your application a familiar field.

The map reads the order number and returns it as JSON. The value stays PO0001; your application can use purchaseOrderNumber without parsing the X12 segment itself.

This small map extracts one field. Your own map can include the line items, addresses, and other values your order system needs. Your integration retrieves mapped documents through the Integration API.

Expected output · JSON

{"purchaseOrderNumber": "PO0001"}

Same order, usable field.
X12 order number → JSON purchaseOrderNumber

See how the map reads it

ST->BEG(03) selects the third element of the order header.

purchaseOrderNumber = ST->BEG(03)
"{\"purchaseOrderNumber\": \"" + purchaseOrderNumber + "\"}"

Download this map or follow the reproducible mapping example.

Next: check the processing evidence

3 · The processing evidence

Know where to look when an order is missing.

In a connected workspace, Activity keeps the original document, mapped output, and related receipts together. Use them to separate delivery questions from mapping questions before investigating your application’s import.

What to inspect with real traffic · This walkthrough has no live transaction or receipt

Which order arrived?Original X12: Open the received document and check the purchase-order number. For our sample, you would look for PO0001.
What did processing produce?Mapped output and errors: Check whether mapping succeeded and inspect the generated JSON. Confirm that the values match the order before importing it.
What was acknowledged?AS2 receipt and acknowledgments: Inspect the AS2 receipt (MDN) for transport status. Review any required functional acknowledgment separately; a transport receipt alone does not establish business acceptance.

A successful map does not confirm an import into your ERP or order system. Your integration handles that step. When you need to check an order and its related replies together, add an optional conversation check.

Choose your next step

Try the mapping, or talk through your partner setup.

The full mapper is best on desktop and needs no signup. Open Tips and choose Keep a mapping working (optional) to practice reading PO0001, changing the map, and checking the result. Close any active lesson first.

Try the mapper — no signup Discuss your partner setup

Ready to connect? Compare plans and the signup steps.