Passer au contenu principal / Skip to main content
← All articles
Systems & integrations2 min read

One product page can bring together several ERP item codes.

Buyers choose a product model and its specifications. Behind the scenes, your ERP still needs the exact item code for the selected variant.

Generated conceptual composition: on warm ivory stone, three pairs of work gloves in varying sizes and tones (charcoal, grey knit and amber wrist trim) are grouped around a single blank graphite-and-ivory master product card.
One product page to simplify the buyer’s choice, while sending the exact item code to your ERP.

A single model of industrial glove often comes in several sizes and colours. To the buyer, that is one product where they pick the size they need. To your ERP, every combination carries its own item code.

Without a clear structure connecting the two, teams end up copying the same description across ten listings or recreating items manually outside the ERP. As the assortment grows, keeping everything up to date gets heavier fast.

Share model content while keeping variant codes exact.

A clean split gives each layer a clear job: the parent product page holds the shared overview, photos, applications and spec sheets. Each variant holds the exact SKU needed to resolve customer pricing, check inventory and place the order.

One common setup keeps shared marketing content in a PIM tool and links each variant back to ERP items, though other arrangements work equally well if product information already lives cleanly elsewhere.

Connecting buyer selection to the right ERP item code
  1. 1. Model pageShared copy, imagery and technical sheets maintained once for the product family.
  2. 2. Variant choiceThe customer picks size, colour or configuration on a single page.
  3. 3. Exact ERP codeCheckout passes the precise SKU needed for pricing, stock and fulfilment.

Illustrative split. Ownership of each data field always depends on your existing systems.

Clarify which system owns each piece of data.

Boutik can assemble product data from each source without forcing every company into one rigid toolset. What matters most is defining the mappings between families, variants and ERP item codes, and agreeing on which system owns each field.

Once ownership is explicit, teams avoid double maintenance and updates from the ERP never silently overwrite enriched descriptions.

A quick check across one product family

  • ✓ Pick one product line offered in multiple sizes, materials or configurations.
  • ✓ Trace it end to end: what the buyer sees, what options they select and which SKU lands in the ERP.
  • ✓ Spot every step where your team still copies descriptions or re-enters item data by hand.
Review your catalogue structure ↗

AN IDEA WORTH SHARING

Keep the conversation going.

Share on LinkedIn (new tab) ↗Share on Facebook (new tab) ↗Share on X (new tab) ↗