Choose the basis for calculating the price excluding or including tax

The processing of VAT, rounding, and large sales volumes starts with the price base of the transaction. When VATLESS_BASE_PRICE is enabled, the system treats the source price as tax-free: the net price of the line is rounded and tax is added to it. When this setting is disabled, the source price is tax-inclusive: the gross price is rounded and the net and tax are derived from it.

Different calculation bases can produce cent-level differences. Do not change the setting in production just because of a display difference. First, clarify the source system, tax categories, currency calculation accuracy, calculation of orders and quotes, and the meaning of already saved prices.

Set the source price consistently

Handling VAT, rounding, and large sales volumes requires the same price basis in ERP, PIM, and AI Commerce . If the master system delivers a tax-free price, use the tax-free source price. If it delivers a tax-inclusive price, confirm the tax-inclusive calculation path in the integration agreement.

The store's price basis determines whether the monetary source values in the dashboard are interpreted as tax-free or tax-inclusive. The same rule applies to the Base Price of products and to shipping prices, payment method surcharges, and small order and invoicing surcharges stored in the store settings. In a store using a net price, the values are entered tax-free; in a store using a gross price, they are entered tax-inclusive. Do not change the basis for an individual field or add VAT a second time. The live price of an external shipping service is not the store's own set price.

Understand the accuracy of package size calculation

Handling VAT, rounding, and large sales quantities typically uses two decimal places in the standard price. When the Pack Size is greater than 1, the current price format uses the maximum calculation precision defined for the currency. The current inventory balance import description then reports 6 decimal places and otherwise 2 decimal places.

Six decimal places is a calculation precision, not a promise that all views, payment services or invoices will display six decimal places. Line amounts, tax and totals may be rounded to two decimal places in different interfaces. Therefore, test the entire path from source price to cart, order, payment, invoice and ERP export.

Specify minimum quantity and quantity step

Handling VAT, rounding, and large sales quantities uses the Minimum Quantity field on the product for the smallest allowed purchase quantity. The quantity step determines the increment and decrement step of the cart. For example, a step of 5 allows quantities of 5, 10, and 15, but not quantities of 6 or 7.

Don't assume that the UI will automatically correct any incorrect input to the next value. In addition to the storefront quantity picker, verify server-side validation, direct cart call, variants, decimal quantities, inventory balance, and boundary cases. Minimum quantity and step are different rules, and both must be met.

Specify packaging size and packaging unit

Handling VAT, rounding and large sales quantities uses the Package Size field for the number of basic units in the package. The packaging unit is selected from the register and is displayed in the online store next to the price, for example per liter or per piece. An unknown register ID must be corrected before saving.

The current unit price formation uses the pack size, quantity step, and pack unit together. However, this does not mean that you should set the pack size for every product to be greater than 1. Use values only according to the actual sales quantity and unit price.

Test net, gross and VAT amounts

The handling of VAT, rounding, and large sales quantities is tested with at least one product based on a tax-free and tax-based source price. Calculate the expected unit price, quantity, line net, VAT portion, gross, and total with the same accuracy as the implementation.

Try the standard pack size 1 and pack size over 1. Add the minimum quantity to the cart, one more step and the forbidden quantity. Compare the product page, cart, checkout, order, payment and ERP/PIM message. Document each cent difference to the calculation step where it occurs.

Deployment checklist

The processing of VAT, rounding, and large sales quantities is only complete when:

1. The tax-free or tax-inclusive price basis of the transaction is documented.
2. The source price for ERP, PIM, and AI Commerce means the same thing.
3. Tax categories and currency calculation accuracy have been confirmed.
4. The Base Price, Minimum Quantity, Quantity Step, Package Size, and Packaging Unit are set according to the actual sales method of the product.
5. Package sizes 1 and above 1 and limit cases of quantities have been tested.
6. The product page, cart, order, payment, invoice, and integration amounts match the accepted rounding rule.

Act in a controlled manner when deviating

When handling VAT, rounding, and large sales quantities, the discrepancy is not corrected by randomly changing the price, tax rate, or decimal number. Record the product, source price, price basis, tax rate, package size, quantity step, quantity, and the net, tax, and gross amounts for each step.

First, determine whether the difference occurs in the source system, import, pricing, cart, payment service, invoice, or ERP export. Only change the contract in the system that owns the incorrect step and ensure the fix with the same borderline cases.