Integrating Inventory with Items Service

Architecture overview

Items Service serves as the single source of truth for item identifiers across the platform. It provides Inventory Service with a validated, unique identifier (ID) for every item type (whether it is a product, stock keeping unit (SKU), or Global Trade Item Number (GTIN)).

Instead of relying on localized, static database tables, Inventory Service queries Items Service dynamically to cross-reference data. The service then fetches enriched item metadata, including the ItemId from the Items service and additional metadata, such as the item's name and description, from the Catalog service.

Previously, Inventory Service relied on static catalog data loads or manual file uploads to recognize items. Any modifications to existing SKUs or the introduction of new products required a complete data reload. This bottleneck created a reliance on batch-driven updates, caused data staleness, and disrupted core workflows.

Affected components include:

Configure Items page
PO Imports
Vendor Imports and Vendor-SKU Associations
Receiving flow

Core validation matrix

The behavior of core inventory modules relies on the following real-time validation matrix:


Workflow component	Validation rule and action	System behavior on failure
PO Imports	Cross-references Items Service to ensure the SKU exists	Blocks import: Restricts the purchase order line item if the identifier is missing
Vendor-SKU Association	Validates SKU existence before allowing an association to be saved	Blocks action: Denies creation of the vendor association
Receiving flow (Existing identifier)	Validates incoming item against live identifiers and checks for decommissioned flags	Blocks receipt: Restricts entry of decommissioned or invalid items
Receiving flow (Valid item, missing configuration)	Validates item existence when an item lacks a pre-configured inventory profile	Allows receipt and auto-setup: Processes the receipt seamlessly, generates a default item-level configuration, and sends a system notification

Note: If an item arrives at the warehouse without a pre-existing localized inventory configuration, but the item exists validly within Items Service, the system does not block the workflow. You can complete the receipt successfully. During initial data load the system loads global inventory configuration settings for all items. Which can then be overridden per channel from Inventory tooling.

Success metrics

Engineering and product teams track specific key performance indicators (KPIs) and telemetry data to measure integration success.


Key Performance Indicator	Target Objective
Validation Accuracy	Maintain a 100% success rate in cross-referencing and verifying SKU existence during PO imports and Vendor-SKU association setups.
Data Refresh Latency	Minimize the time it takes for Inventory Service to recognize a newly created item ID compared to legacy batch timelines.
Error Rate Reduction	Decrease the number of failed or incorrect receipts of non-existent or decommissioned items during warehouse receiving.

Configuration continuity

SKU-level continuity: Core inventory configurations continue to function when keyed by the new Item ID.
Channel overrides: Users can set and enforce channel-specific inventory overrides for the same item to ensure zero disruption to existing rules.