order_processing · ecommerce · workflow

Snack food giant saves millions and automates order management with OpenText Trading Grid

Mondelēz Brazil's third-party B2B integration provider made limited use of EDI, leaving sales professionals to manually type orders for hours, which caused costly entry errors and returns worth millions of dollars, while poor provider support left the team stuck in global ticketing queues.

How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · PDF order document received
Unstructured PDF order documents arrive from clients, each using unique SKUs mapped via cross-reference tables.
Tools used
OpenText Trading GridOCR
Outcome

OpenText Trading Grid uses OCR to convert PDF orders into structured EDI data automatically transmitted to SAP ERP, with Trading Grid Intelligence validating, flagging discrepancies, and routing orders to the correct distribution center, saving millions and freeing sales teams from low-value data entry.

What failed first

A third-party B2B integration provider took over SAP ERP connectivity but made limited use of EDI, forcing manual order entry. When problems occurred, support was unreachable and the team was stuck in global ticketing queues.

Results
Time savedhours manually typing orders
Cost replacedsaves millions
Source

https://www.opentext.com/customers/mondelez-brazil-edi-order-automation

How we source this →

Grounding & classification
Source type: vendor customer story
26 fields verified against source quotes, 2 dropped as unverifiable.
data extractiondocument aiocrpurchase orderfailure mode describedmetric backednamed customerproduction runtime claimedworkflow describedmanufacturingretailcost reductionemployee productivityerror reductiontime savedvendor customer storyorder processingsupply chaindocument to recordextract classify route