AgentBIAgent with Business Intelligence for DTC sites

Back to the knowledge base

OPT-3

Unify SKU↔id mapping and unit / size conversions

Published:2026-11-18Views:0

When the same product carries different IDs in ERP, storefront and feed, agents comparing them split it into two items; units and size conversions scattered in copy fail to line up across markets. A single SKU-to-page-ID mapping and unit definition is one of the earliest data-layer tasks.

Build a mapping table: each SKU maps to one public ID, with aliases and old IDs kept as traceable entries. Put weight, dimensions and size conversions in master data with explicit definitions (metric/imperial, net/gross), and have both product pages and feeds read from it. Product markup references the same ID so the view layer never rewrites identifiers.

A unified mapping solves identity and unit consistency only. It performs no cross-channel matching and issues no verdict on any comparison result; conversion standards follow the owner's own definition, and this site generates no product data.

Official references

2026-11-22