Conflicting Product Sheets and Missing Packaging Data: Personal Care Agent Exceptions

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

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.

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.

Technical references

• Stacksync Workflows quick start
• Stacksync NetSuite supported objects