--- title: "Orderful NetSuite EDI mapping for beauty shades and sets" description: "Retailer item numbers on Orderful purchase orders resolve to the NetSuite shade, size or set revision, and that line survives through ASN and invoice." canonical: https://www.stacksync.com/blog/personal-care-retail-edi-match-retailer-item-numbers-to-shades-sizes-and-sets last_modified: 2026-09-21 --- # Personal Care Retail EDI: Match Retailer Item Numbers to Shades, Sizes, and Sets > 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 Each retailer item code carries an effective set definition, so a reused seasonal code or a warehouse shade swap cannot rewrite what the retailer ordered. Author Alexis Favre · Co-Founder & CTO Published September 21, 2026 Read time 4 min read APP TIPS ## The operating decision Personal-care retail EDI requires an exact crosswalk from retailer item numbers to shades, sizes, and sets. Preserve the partner’s line and packaging definition through order acceptance, shipment, and invoice. Technical document validation cannot detect every commercially wrong product mapping, so verify item meaning before release. Explore the complete [personal care integration and automation hub](https://www.stacksync.com/industry/cpg/personal-care) for the systems and processes around this guide. ![Summary card: Orderful NetSuite EDI mapping for beauty shades and sets](https://www.stacksync.com/images/blog-highlights/icp-personal-care-retail-edi-match-retailer-item-numbers-to-shades-sizes-and-sets.webp) ## What this looks like in personal care A retailer orders a seasonal gift set under its own item number. The brand also sells the component products individually and the set changes next season. The EDI mapping needs the current approved set revision while preserving older orders, rather than treating the retailer item as a timeless alias for one component. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Retailer item code | Product operations | Map the code to exact shade, size, set, and effective packaging definition. | | Partner order line | Retail operations | Retain line reference, quantity, unit, destination, and requested dates. | | Shipment item evidence | Warehouse | Use actual packed items and approved substitutions only. | | Mapping revision | Integration owner | Track tested partner rules and effective product relationships. | ![Record ownership diagram: Retailer item code, Partner order line, Shipment item evidence](https://www.stacksync.com/images/blog-diagrams/icp-personal-care-retail-edi-match-retailer-item-numbers-to-shades-sizes-and-sets.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Approve the assortment mapping Review each retailer code against the intended consumer product and case configuration. Similar shade names or shared family codes should not bypass exact item validation. 2. 02 Preserve set revisions Tie seasonal sets to approved components and effective dates. Before changing a mapping, inspect open orders and determine which version the retailer actually ordered. 3. 03 Build documents from their owners Acknowledgments use the accepted commercial decision, shipment notices use actual packing evidence, and invoices use the finance-owned transaction. Keep the partner references consistent across the chain. 4. 04 Test product exceptions Include wrong shade, changed set, partial shipment, and unknown retailer item cases. Confirm both technical acceptance and the business correctness of the mapped products. 5. 05 Push last season's retailer code through the Orderful test stream In the Orderful test stream, submit a purchase order using a retailer item number from last season's gift set, now assigned to this season's set. The NetSuite sales order must show the current revision's components with its effective date, while last season's accepted orders under the same code keep their original components. If earlier orders now display the new set, the mapping has no effective dating and cannot go live. Ship the test order and raise the invoice. Compare the retailer's line number on the purchase order, the ship notice and the invoice: all three must match. A renumbered or dropped line means the partner reference is regenerated, not carried. ![5-step operating sequence: Orderful NetSuite EDI mapping for beauty shades and sets](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-personal-care-retail-edi-match-retailer-item-numbers-to-shades-sizes-and-sets.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Retailer reuses a seasonal code Confirm the effective set definition instead of rewriting historical orders. ### Warehouse proposes another shade Require commercial approval and the partner-compliant representation. ### Set ships in separate cartons Preserve the actual shipment hierarchy required by the partner. ## What to verify before expanding - Every retailer item resolves to the intended shade, size, or set revision. - The original partner line survives through shipment and invoice reconciliation. - A reused seasonal retailer code preserves the historical set definition for already accepted orders. - A proposed shade substitution requires the accepted commercial decision and partner-compliant representation before release. ## Connect this process to the rest of your operation [Explore Stacksync EDI](https://www.stacksync.com/edi) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real retailer item code example and the exception your team handles most often, for example retailer reuses a seasonal code. - [Shopify–NetSuite Sync for Personal Care Brands: Align Shades, Sizes, and Gift Sets](https://www.stacksync.com/blog/shopify-netsuite-sync-for-personal-care-brands-align-shades-sizes-and-gift-sets) - [Amazon–NetSuite Sync for Beauty Brands: Match Variation Families to ERP Products](https://www.stacksync.com/blog/amazon-netsuite-sync-for-beauty-brands-match-variation-families-to-erp-products) - [HubSpot–Acumatica Sync for Personal Care Brands Selling to Salons and Retailers](https://www.stacksync.com/blog/hubspot-acumatica-sync-for-personal-care-brands-selling-to-salons-and-retailers) - [EDI Compliance Issues with Retail Trading Partners (2026 Guide)](https://www.stacksync.com/blog/edi-compliance-retail-partners-trading) - [Product Exchange Checks: Refunds, Stock, and Customer Choice](https://www.stacksync.com/blog/product-exchange-checks-refunds-stock-and-customer-choice) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Orderful transaction model](https://docs.orderful.com/reference/orderful-transactions) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Can one product-family mapping cover every shade? No. The retailer orders specific sellable items. Family context can help navigation, but the transaction mapping must preserve the exact item and packaging. Is passing Orderful validation the same as the mapping being right? No. Orderful checks the document against the partner's guideline: required segments, formats, and codes the retailer will accept. It has no view on whether the shade behind your item number is the one the buyer meant. Treat a clean validation result as permission to transmit, and treat a product-operations sign-off on the crosswalk as permission to ship. Both have to hold before the live stream opens. When a retailer adds a shade to a set, what happens first? Product operations creates or confirms the NetSuite item, then the integration owner adds a dated crosswalk row for the retailer code and runs the partner's test transaction against it. Only after that does the live relationship accept orders for the new shade. Reversing the order, mapping the code before the item exists, leaves incoming orders unmatched in the review queue, which is the safe outcome but a slow one. About the author Alexis Favre Co-Founder & CTO Alexis Favre is the Co-Founder and CTO of Stacksync (YC W24), the first real-time and two-way sync for enterprise data at scale. Alexis is a Y Combinator alumni with expertise in large scale data engineering. [All posts by Alexis Favre](https://www.stacksync.com/blog/author/alexis-favre) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Orderful integrations](https://www.stacksync.com/connectors/orderful) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv 4 min read read](https://www.stacksync.com/blog/personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv) [App tips Personal Care Sample and Tester Workflows: Track Requests Through Warehouse Fulfillment 4 min read read](https://www.stacksync.com/blog/personal-care-sample-and-tester-workflows-track-requests-through-warehouse-fulfillment) [App tips AI Agents for Personal Care Retailer Onboarding: Assemble Product and Packaging Documents 5 min read read](https://www.stacksync.com/blog/ai-agents-for-personal-care-retailer-onboarding-assemble-product-and-packaging-documents) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)