When syncing products from Business Central to Centra (or another e-commerce platform), product variants — sizes, colours, dimensions — need to be correctly mapped between the two systems. Business Central and Centra use different conventions for representing variant data, and a missing or incorrect mapping is one of the most common causes of product transfer failures.
How variant mapping works
Business Central stores variant attributes as dimension values — typically a code like ONE, S, M, XL, 2Y, 10Y, or 146/152 (11-12Y). These are the exact string values that Junipeer receives from the BC API.
Centra organises sizes into size charts — named groupings such as XXS-XXL [id: 2], Kids [id: 3], or One Size [id: 1]. Each product variant in Centra must belong to one of these charts.
The Size Chart Setter in Junipeer is where you create the mapping between BC dimension values and Centra size charts. Every dimension value coming from BC must have a corresponding row in the Size Chart Setter, or the product transfer will fail for variants that use that value.
Setting up the Size Chart Setter
Navigate to your integration settings and open the Size Chart Setter configuration.
For each BC dimension value you expect to receive, add a row:
Business Central Variant Dimension value — enter the exact value as it appears in BC (e.g.
146/152 (11-12Y),ONE,XL)Centra Size Chart — select the Centra size chart this value belongs to (e.g.
Kids [id: 3],XXS-XXL [id: 2],One Size [id: 1])
The BC dimension value must match exactly — including capitalisation, spaces, and special characters. A value of
xlwill not matchXL. A value of146/152 (11-12Y)will not match146/152.
Repeat for every size/dimension variant used across your BC product catalogue.
Common size chart groupings
A typical fashion brand mapping looks like this:
| BC Dimension Value | Centra Size Chart | |---|---| | ONE | One Size [id: 1] | | XXS | XXS-XXL [id: 2] | | XS | XXS-XXL [id: 2] | | S | XXS-XXL [id: 2] | | M | XXS-XXL [id: 2] | | L | XXS-XXL [id: 2] | | XL | XXS-XXL [id: 2] | | 2Y | Kids [id: 3] | | 4Y | Kids [id: 3] | | 6Y | Kids [id: 3] | | 8Y | Kids [id: 3] | | 10Y | Kids [id: 3] | | 12Y | Kids [id: 3] | | 146/152 (11-12Y) | Kids [id: 3] |
Your actual Centra size chart IDs may differ — always verify the IDs in your Centra admin before setting up the mapping.
What happens when a mapping is missing
If a BC dimension value arrives that has no corresponding row in the Size Chart Setter, the product variant transfer will fail with an error indicating that the size chart could not be determined.
The fix is always the same:
Identify the exact BC dimension value from the error log or the Junipeer Entities page
Add a new row in the Size Chart Setter for that value
Re-run the product transfer
Tip: When onboarding a new BC ↔ Centra integration, export your full list of BC variant dimension values first and map them all before running the initial product transfer. This prevents a long tail of individual failures as new values are encountered one by one.
Keeping the mapping up to date
BC dimension values can be added over time — for example when a new clothing line introduces new size codes. Whenever new variant dimension values are added in BC, remember to add the corresponding row in Junipeer's Size Chart Setter before running the next product transfer.
A quick way to catch missing mappings before they cause failures: after adding new products in BC, check the Junipeer Entities page for any product variants with a failed or pending status, and trace the error back to the Size Chart Setter.
For related error codes, see the Error Codes reference. For general BC setup, see Business Central Setup.