Yes — a dated 10% pre‑payment checkout record can be supported by discrete fields recorded at the “stop‑before‑payment” stage, but it does not guarantee that the code currently works for every reader or that payment, shipping, fulfilment, eligibility, or product quality will follow. Below I map exactly which data fields, and what values in those fields, support the claim “10% off” at the pre‑payment cart step, and offer a practical approach to evaluating that evidence.
Why this matters: a clear, dated snapshot of a cart showing subtotal, discount, and resulting total is the evidence type needed to support a pre‑payment percentage discount claim. Without those fields, a code string alone or an undated note is incomplete.
What to look for (worked field map) Below is a worked map of the minimal, concrete fields you should expect to see in a dated pre‑payment checkout record that supports “10% off.” Each field is defined, and I explain how the value contributes to the claim.
- Code string
- Definition: the exact alphanumeric token entered or applied (e.g., “GROWTH10”).
- Why it matters: identifies which discount was applied at the time of record. The presence of a code string alone does not prove the discount amount — you must pair it with the monetary fields below.
- Timestamp
- Definition: a precise date and time when the cart was captured (ideally including timezone).
- Why it matters: establishes when the record was made; dating is required because promotional availability can change. A dated record anchors the record in time.
- Item (line descriptions)
- Definition: list of cart line items with names, quantities, and unit prices for each SKU or product line.
- Why it matters: allows verification that the subtotal calculation corresponds to the shown items. It helps detect examples where a discount applies only to specific SKUs.
- Currency
- Definition: the currency code used in the cart (e.g., CAD, USD).
- Why it matters: percent and monetary calculations must be interpreted in the correct currency. A “10%” result in one currency is not evidence about another.
- Subtotal (pre‑discount)
- Definition: the total of line items before any discount is applied and before taxes and shipping are added.
- Why it matters: the percent discount claim is normally calculated from this number. You need the subtotal to check that a 10% reduction was applied correctly.
- Discount (displayed amount and label)
- Definition: the monetary amount deducted and any label describing the discount (e.g., “10% off with GROWTH10”).
- Why it matters: the label links the code string to the monetary discount. The discount amount must match 10% of the subtotal (subject to rounding or per‑item rules) to support “10% off.”
- Resulting total (pre‑payment, after discount)
- Definition: the cart total after discounts, but before payment is submitted — excluding separate shipping and tax entries unless shown as part of the pre‑payment total.
- Why it matters: confirms the arithmetic — subtotal minus discount equals the resulting total. If this holds, the record supports that a 10% reduction had been applied at that stage.
- Stop‑before‑payment boundary
- Definition: evidence that the snapshot was taken at the cart or checkout review page before the final “Pay” or “Submit order” action.
- Why it matters: distinguishes a pre‑payment record from a completed payment or fulfillment record. This boundary is essential to avoid inferring payment, shipping, or fulfillment from the cart snapshot.
How these fields combine to support “10% off” To claim a dated 10% pre‑payment record, you need at minimum:
- A timestamped capture showing a code string was present or applied [code string + timestamp].
- A visible subtotal and a discount amount where Discount ≈ 0.10 × Subtotal (allowing for stated rounding rules) [subtotal + discount].
- A resulting total that equals Subtotal − Discount [resulting total].
- A clear indicator that the capture was taken before payment submission (the stop‑before‑payment boundary).
When those elements appear together in a single dated snapshot, the evidence supports the narrow proposition: “At this timestamp, applying that code produced a 10% reduction on the cart total before payment.” Sources that archive such snapshots and explain verification methods help contextualize how that evidence was collected and preserved [1] [2] [3].
Practical checks and common caveats
- Check labels and scope: confirm the discount label ties the code string to the monetary discount (e.g., “GROWTH10 — 10% off” appearing next to the discount line). If the discount line lacks a label, the code string and discount may be unrelated.
- Watch per‑item vs. cart‑wide rules: some discounts apply only to specific SKUs or categories. Line‑item details let you see if the discount covered all items or only some; if it covered only some items, the claim “10% off the cart” is weaker.
- Rounding and thresholds: small discrepancies can arise from per‑item rounding or minimums/maximums. Evidence should show how the discount was calculated (per‑item vs. subtotal).
- Stop‑before‑payment is key: the record must show the checkout stage, not a confirmation email or post‑purchase receipt. A confirmation email establishes payment occurred; a pre‑payment cart snapshot does not.
- Dated record ≠ universal availability: a single dated snapshot is a historical fact about that moment. It does not prove the code will work now, for other users, or for different carts.
How archival and verification notes help Documentation that describes verification procedures and preserves dated snapshots increases confidence that the capture is authentic and unaltered. Look for an explanation of how timestamps were recorded and how snapshots are archived or indexed. Such meta‑documentation clarifies what the archived page actually establishes and what remains unresolved (for example, whether the capture came from a live session or a staged test) [2] [3].
Summary checklist To read a claimed “10% pre‑payment cart” record use this quick checklist:
- Is there a clear timestamp? (yes/no)
- Is the code string visible? (yes/no)
- Is the subtotal shown and does Discount ≈ 0.10 × Subtotal? (yes/no)
- Does the resulting total equal Subtotal − Discount? (yes/no)
- Is the capture explicitly at the pre‑payment/checkout review stage? (yes/no)
If the answer is “yes” to each, the snapshot supports the narrow claim that a 10% discount was applied at that time and stage. If any item is missing or ambiguous, the strength of the evidence falls accordingly. For explanations of how individual captures are verified and preserved, see the verification desk documentation and archive examples [1] [2] [3].
References
Current evidence
Read the current GROWTH10 verification record
Current cart evidence and historical records are maintained separately from this editorial guide.
Open the current record →