What a trade pricing engine actually has to get right

Money is the part you cannot get wrong

A trade order is not one price. It's a base price, adjusted for size, for made-to-measure, for chosen options, then discounted by the retailer's terms, then taxed - and every one of those steps has to land on a figure both sides trust.

One source of truth

The mistake is to compute prices in the browser, or in three different places that drift apart. On Labels.io there is a single pricing engine. It runs server-side, it's the same code for the configurator, the basket and the final order, and it's reconciled against the label's original price lists.

Rounding is a policy, not an accident

If you round at the end, your line items won't sum to your total. If you round each step, they will - but you have to choose that on purpose and test it. We pin the behaviour with a suite of golden scenarios drawn straight from the label's own workbook: if a total ever drifts by a penny, the build fails.

Why it matters

Retailers place bigger orders in a system they trust. Penny-accurate, every time, is how you earn that.