Try our new AI assistant by clicking the chat icon in the lower right corner.
With Miva’s Precision Pricing capability, merchants can now price products at less than a penny, which is helpful for stores that sell small products, like industrial fasteners, in mass quantities. Specifically, prices can be set to eight decimal places, allowing for prices as low as $0.00000001.
Adding precision pricing or weight may have unexpected consequences when using third party integrations that use these data fields. If, for example, you create a $0.005 product, it is not appropriate for us to decide that this should be exposed differently in the API. That could also create unexpected consequences, so we leave it to our customers to make these decisions and deal with these consequences downstream.
Precision Pricing requires no configuration after upgrading to Miva version 10.11.00. In fact, most customers will still use the standard two decimal places and see no change.
Behind the scenes, different calculation and data storage rules are applied when Miva finds a product where more than two decimal places have been assigned, for example as a product weight, product price, or in volume discounting table.
Here’s an example of a volume discount table showing discounts. The actual product is priced is $0.5596 (not shown) and weight is stored to precision, 0.01344358 lbs.
What the customer would see is, and appropriately, they are seeing high precision pricing because this is a per unit price.
If a customer adds 1001 of this item to the basket, they see this, a much more appropriate, two-digit total cost.:
At an order level, for a product with Precision Pricing, none of the precision-rich data is lost and is reflected in the order information.
While in the database, even though the basket is presented with two decimal places, the precision price information is retained.
Any integration that uses the Miva API to pull orders, also receives rich, precision pricing and weight data.
To ensure downstream compatibility, Miva adapts native integrations that do not support precision pricing where they require us to send a quantity.
For example, In places where it would break to send this information:
Item: #12 WIDGET
Quantity: 1001
Price: $0.07884
Total: $78.92
We instead send:
Item: (Qty: 1001) #12 WIDGET
Quantity: 1
Price: $78.92
Total: $78.92
In this case, for PayPal:
Notably, TaxJar DOES support precision pricing and we send it rich precision pricing data when available.