Map vendor items without assuming SKUs are globally unique
Two tenants both sell SKU CABLE-2M, and a mapping lookup updates the wrong stock row. Scope vendor mappings by tenant, connector, warehouse, and vendor item identity.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Tenant isolation · Identity mapping · Database constraints
Estimated field mix
- Integrations40%
- Security30%
- Database engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional retailer receives stock from two vendor warehouses. The vendor API paginates snapshots and emits change events, but retries and deleted products have caused unexplained stock drift. Work against a local vendor simulator.
Setup prerequisites
- Create a local vendor API simulator with cursor pages and stock events.
- Use synthetic tenants, SKUs, and warehouse records; no vendor account is required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Mapping lookup always requires server-derived tenant and connector scope.
- Unique constraints prevent duplicate mapping identities within that scope.
- Unmapped or ambiguous items are quarantined and do not update a guessed SKU.
Implementation constraints
- Treat display SKU as mutable metadata, not a durable identity.
Verification to include
- Map identical SKU text for two tenants and verify each stock update stays in its own tenant.
- Supply an unmapped vendor item and confirm no stock mutation and an inspectable mapping issue.
Deliverables
- Scoped mapping repository and cross-tenant tests
Rollout and recovery
Backfill explicit mapping identities before enabling updates; pause connectors with unresolved mapping conflicts.
Value of the work
For the engineer: Practice external contracts, cursor recovery, mapping conflicts, and reconciliation under partial failure.
For the team: Inspect whether integration changes protect inventory correctness and give operators a clear recovery path.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.