Skip to content
Engineering

What Actually Breaks When You Sell Across Borders

Zero-decimal currencies, countries with no postal codes, and tax embedded in prices — the concrete failures waiting in your international expansion, and how Commercefull handles each one.

October 28, 2026

Every platform demo sells “multi-currency, multi-language” like it’s a flag on a settings page. Then you flip the flag and the real problems surface — the ones nobody puts in the demo.

Here are the concrete failures that hit international commerce, and where Commercefull’s global-commerce work addresses each one.

The ¥1,499 rounding bug

Japanese yen has zero decimal places. Kuwaiti dinar has three. If your money handling stores amounts as floats, or assumes two decimals, ¥1,499 either gets a phantom “.99” appended or rounds unpredictably in tax and discount math.

Commercefull’s libs/money is ISO-4217-aware — minor units derive from the currency’s actual exponent. A JPY checkout computes ¥1,499 + ¥800 shipping as exact integer minor units, no float drift. We test it as an end-to-end scenario: seed a JPY-priced product, check out on a JPY market, assert the exact totals.

“Postal code is required” — except it isn’t

The UAE doesn’t use postal codes. Belgium doesn’t need a state/province field. The US absolutely does. If your address validation is if (!postalCode) reject() — a pattern we’ve literally found and removed in our own legacy code — you’ve just rejected every customer in Dubai.

Commercefull ships countryAddressMetadata — per-country address field rules (required/optional fields, admin-area requirements, field labels) — and both the checkout validator and the storefront form resolve from it. The form toggles fields per selected country; the API validates against the same metadata. One source of truth, no country if statements.

“The price is $100” — is tax inside or outside?

US convention: the price tag excludes tax; it’s added at checkout. UK/EU convention: the displayed price includes VAT. A platform that picks one breaks the other — either your UK customers get sticker shock at the final step, or your US order totals show tax baked in where it shouldn’t be.

Each Store/Market in Commercefull declares taxDisplayMode — exclusive_tax or inclusive_tax — and the cart, checkout, and order totals follow it per market. Bonus for B2B: a validated EU VAT registration gets reverse-charge treatment in intra-EU flows, recorded per order line.

The order audit nobody can do later

“Why did this order get charged 21% VAT in January when the rate is 20% now?” On most platforms: archaeology. The tax engine changed; the order just has a number.

Commercefull orders persist a version snapshot and decision log — which market version, which tax regime and policy version, which promotion rules fired, with inputs. GET /business/orders/:orderId/decisions replays the reasoning months later, and historical refunds replay against the snapshot — not today’s rules.

The honest boundary

Address metadata doesn’t teach a platform a carrier API it never integrated, and markets don’t conjure a PSP rail that doesn’t exist. New external protocols still need adapters — but they land behind ports, not as #if COUNTRY branches. Expansion stays configuration-driven; the exceptions are bounded and honest.

Read more

Ready to own your store?

Commercefull is free, open-source, and Apache-2.0 licensed. Every module, every line, every row of data — yours.