Price fields: amount, currency and stated conditions
Retain the amount, currency, unit and stated conditions of a price observation. An Olivit reference with fictional records for a data export.
Advox’s Olivit case describes replacing a tightly coupled B2B platform with a modular system. Its pricing service handles individual price lists, product promotions and cart discounts, with calculations that include currency conversion and promotion priorities. The provider reports these functions as implemented. This is Advox’s project account; it does not publish the underlying exchange-rate source, tax treatment or individual price-resolution tests. The following method concerns the structure of a separate data delivery.
Give every amount its own context fields
For a marketplace-data export, PandaBuyNow proposes retaining the displayed amount and original price text alongside a currency field. Record the listing and selected variant, observation time, price type, visible audience or channel, and the unit to which the amount applies. Keep a stated tax label or inclusion note as source text; preserve an absent label as unknown.
Separate a listed price from a cart amount, customer-specific price or calculated conversion. Use a field definition to explain which kind of amount each row contains. A repeated number does not establish that two rows express the same offer.
Test the file with fictional price observations
Consider invented variant CUP-P. One source displays “EUR 72 per case” and names six pieces in the selected case. Retain the amount, currency, case unit and piece count as separate fields with their source reference. Its tax label is absent, so the tax-basis field remains unresolved.
A second observation displays USD 72, but does not establish a case quantity or price type. Give it a separate record and quality note. These rows do not support treating the offers as equivalent. Their invented labels and amounts describe no Olivit or PandaBuyNow transaction.
Keep transformations visible in the delivery
If the agreed output includes converted or per-unit amounts, retain them separately from the source amount. Include the formula or mapping version and the supporting rate or quantity reference where supplied. Leave a transformation unresolved when its inputs or meaning are missing. Record rounding and numeric-format conventions in the field definitions so the recipient can reproduce the file’s interpretation.
For a PandaBuyNow discussion, provide representative public listing links, the price fields needed and the expected JSON or CSV structure. Agree feasible collection, source references, transformation rules and data-quality notes through a small data excerpt. The customer decides how to use the delivered observations; the export does not set prices or determine tax treatment.