--- title: "EDIFACT ORDCHG Purchase Order Change Request | Stacksync" description: "EDIFACT ORDCHG Purchase Order Change Request: mapping identifiers, validation examples, related messages and 1 partner references." canonical: https://www.stacksync.com/edi/edifact/purchase-order-change-request last_modified: 2026-09-15 --- EDIFACT transaction code # EDIFACT ORDCHG Purchase Order Change Request > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDIFACT ORDCHG Purchase Order Change Request: explore its business purpose, mapping identifiers, validation tests and 1 partner references across 1 listed channels. Standard EDIFACT Code ORDCHG Partner references 1 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) Implementation guide ## EDIFACT ORDCHG mapping and validation EDIFACT ORDCHG Purchase Order Change Request is used when a buyer revises an existing order. Preserve original order, revision and affected line so the purchase-order change in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **purchase-order change** original order, revision and affected line | Define which combination of original order, revision and affected line identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the purchase-order change** ID assigned by the receiving system and processing result | Apply a change to the original order without duplicating it. Test a cancellation after dispatch and route it for review. | | Check the processing result | **Processing status for the purchase-order change** Original document reference and matching response | Reconcile the purchase-order change with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### How the related documents differ Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately. - [EDIFACT ORDERS Purchase Order](https://www.stacksync.com/edi/edifact/orders-purchase-order) **purchase order:** a buyer places an order. - [EDIFACT ORDRSP Purchase Order Response](https://www.stacksync.com/edi/edifact/ordrsp-purchase-order-response) **purchase-order response:** a seller responds to an order. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when a buyer revises an existing order. Name the operational owner of the purchase-order change and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map original order, revision and affected line. Confirm qualifiers, code lists, units and date/time meaning against the agreed EDIFACT version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic purchase-order change data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful purchase-order change processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved ORDCHG sample and the agreed version and partner guide are available. - The mapping tests pass with realistic purchase-order change data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out purchase-order change without processing it twice. ### Related documents and resources - [EDIFACT ORDERS Purchase Order](https://www.stacksync.com/edi/edifact/orders-purchase-order) - [EDIFACT ORDRSP Purchase Order Response](https://www.stacksync.com/edi/edifact/ordrsp-purchase-order-response) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [UN/EDIFACT message directory (reference release)](https://service.unece.org/trade/untdid/d04b/trmd/trmdi1.htm) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) ## Find your trading partner for EDIFACT ORDCHG 1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context. - [Amazon](https://www.stacksync.com/edi/amazon) [Amazon DE](https://www.stacksync.com/edi/amazon/amazon-de/edifact-purchase-order-change-request) Catalog breakdown ## Where EDIFACT ORDCHG Purchase Order Change Request appears in this catalog The largest groups of classified ORDCHG catalog entries are in e-commerce & marketplaces. ### By industry - e-commerce & marketplaces 1 channel Partner entries with the most listed channels - [Amazon](https://www.stacksync.com/edi/amazon) FAQ ## EDIFACT ORDCHG questions ### What is EDIFACT ORDCHG Purchase Order Change Request used for? ORDCHG is used when a buyer revises an existing order. It carries information for the purchase-order change. Match it to your business system using original order, revision and affected line. ### Which partners list EDIFACT ORDCHG? The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ### What should I map for EDIFACT ORDCHG? Start with original order, revision and affected line and the target purchase-order change. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test ORDCHG error handling? Apply a change to the original order without duplicating it. Test a cancellation after dispatch and route it for review. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### How does ORDCHG relate to other EDI messages? EDIFACT ORDERS Purchase Order; EDIFACT ORDRSP Purchase Order Response are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete. ### What is the difference between ORDCHG and ORDERS? ORDCHG is used when a buyer revises an existing order. ORDERS is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message. ## Connect EDI to your business systems See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)