--- title: "Genie exceptions for conflicting beauty product sheets" description: "Two approved files give different case dimensions for one lotion: the Genie holds both values, flags the packaging level and waits for the owner." canonical: https://www.stacksync.com/blog/conflicting-product-sheets-and-missing-packaging-data-personal-care-agent-exceptions last_modified: 2026-09-21 --- # Conflicting Product Sheets and Missing Packaging Data: Personal Care Agent Exceptions > 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 Conflicting product sheets, unlabeled packaging levels and absent specs halt the onboarding job with both candidates visible until a product owner names the authoritative source. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision Personal-care document agents should stop at conflicting product sheets, unclear packaging levels, and absent approved specifications. Keep candidate sources and their versions visible, then ask the owner to establish the authoritative value. A newer upload or a similar product is not enough to resolve the conflict. 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: Genie exceptions for conflicting beauty product sheets](https://www.stacksync.com/images/blog-highlights/icp-conflicting-product-sheets-and-missing-packaging-data-personal-care-agent-exceptions.webp) ## What this looks like in personal care Two approved-looking files list different case dimensions for the same lotion. One describes a promotional set and the other the regular product, but filenames are abbreviated. The agent should preserve both candidates and request the packaging identity instead of choosing the most recent upload and filling the retailer’s form. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Conflicting field | Product-data steward | Record both values, units, source versions, and the unresolved identity or scope. | | Packaging level | Operations | Identify consumer unit, inner pack, shipping case, or display configuration. | | Resolution decision | Product owner | Approve the authoritative source and effective product revision. | | Resumed response | Account reviewer | Review changed fields and outstanding gaps before external delivery. | ![Record ownership diagram: Conflicting field, Packaging level, Resolution decision](https://www.stacksync.com/images/blog-diagrams/icp-conflicting-product-sheets-and-missing-packaging-data-personal-care-agent-exceptions.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Classify the conflict Determine whether the issue is item identity, packaging level, document version, or inconsistent approved data. Each category needs a different owner response. 2. 02 Keep units visible Preserve original dimensions, weights, and units. A conversion can normalize a known measurement but cannot decide whether the source described a bottle or a shipping case. 3. 03 Request an authoritative decision Ask the owner for the accepted document or corrected field with effective scope. Do not ask the model to select whichever value seems most plausible for the category. 4. 04 Rebuild affected outputs After resolution, update the relevant packet fields and show their changed sources. Recheck any dependent pack totals or retailer rows rather than leaving derived values based on the rejected source. 5. 05 Load two approved sheets with different case sizes and read the hold Store two product sheets for the same lotion in the document source, both marked approved, one listing the promotional set case and one the regular case, with abbreviated filenames. Run the job. The packet should show the case-dimension row blocked, both values with their file versions, and the document owner named. A filled row using the newer upload means the job is choosing, and it stays in test. After the owner marks one file authoritative, rerun and check the change log: the corrected dimension, the pack totals derived from it, and the reason the other file was rejected should all appear. A stale derived quantity stops the rollout. ![5-step operating sequence: Genie exceptions for conflicting beauty product sheets](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-conflicting-product-sheets-and-missing-packaging-data-personal-care-agent-exceptions.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Both files are marked approved Escalate the source conflict to the document owner and block the affected field. ### Only a similar item has dimensions Leave the requested item incomplete; physical similarity is not approved evidence. ### Retailer changes the requested pack Re-scope the packet and rerun identity and packaging-level checks. ## What to verify before expanding - The packet shows why a source was selected or rejected. - A resolved field triggers review of dependent quantities and dimensions. - Two documents marked approved retain both conflicting values until the document owner resolves the authoritative scope. - Changing the retailer's requested packaging level reopens the affected identity and dimension checks before the packet is sent. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-personal-care) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real conflicting field example and the exception your team handles most often, for example both files are marked approved. - [AI Agents for Personal Care Retailer Onboarding Documents](https://www.stacksync.com/use-case/ai-agents-for-personal-care-retailer-onboarding-documents) - [AI Agents for Personal Care Retailer Onboarding: Assemble Product and Packaging Documents](https://www.stacksync.com/blog/ai-agents-for-personal-care-retailer-onboarding-assemble-product-and-packaging-documents) - [Personal Care Retail EDI: Match Retailer Item Numbers to Shades, Sizes, and Sets](https://www.stacksync.com/blog/personal-care-retail-edi-match-retailer-item-numbers-to-shades-sizes-and-sets) - [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) - [How NetSuite for Retail Transforms Inventory, Finance & Sales](https://www.stacksync.com/blog/netsuite-for-retail) - [Manage Shopify Exchanges Through Zendesk and NetSuite](https://www.stacksync.com/blog/manage-shopify-exchanges-through-zendesk-and-netsuite) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Workflows quick start](https://docs.stacksync.com/two-way-sync/workflows/workflows-quick-start) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Can the agent estimate missing package dimensions? It should not put estimates into an approved retailer packet. Ask the responsible team for the measured, approved specification and clearly retain the gap until then. What distinguishes a version conflict from an identity conflict in the hold? The hold carries the conflict class assigned in the first step, and each class shows a different prompt to the reviewer. A version conflict lists two dates for one file lineage and asks which is effective; an identity conflict lists two item IDs and asks which product the retailer means. The prompt states what the job could not decide, so the reviewer answers that question; both files stay linked from the hold for anyone who wants to check them. Will the job overwrite the stored product sheet once the owner decides? No. The decision is written to the resolution record with the owner, date and effective scope, and the packet is rebuilt from that record. The files in the document store and the NetSuite item stay as they were; correcting master data remains a product-operations task done in those systems. Keeping the job read-only against its sources means a wrong decision can be reversed without repairing the catalog. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) 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 PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [connector Gmail integrations](https://www.stacksync.com/connectors/gmail) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [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) [App tips Manage Shopify Exchanges Through Zendesk and NetSuite 8 min read read](https://www.stacksync.com/blog/manage-shopify-exchanges-through-zendesk-and-netsuite) [App tips Product Exchange Checks: Refunds, Stock, and Customer Choice 7 min read read](https://www.stacksync.com/blog/product-exchange-checks-refunds-stock-and-customer-choice) ## 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/)