On this page
“Reporting included” can mean anything from a dashboard total to a detailed export with stable identifiers and adjustment history. A merchant cannot know whether the feature supports its work until it sees a representative sample and understands the fields.
The procurement task is to test reporting completeness before selection. It is separate from reconciling a live account or calculating campaign performance. The output is an acceptance rubric that shows which required decisions the proposed data can support.
Specify the decisions each report must support
List the decisions the merchant needs to make from the report. Examples include locating the award associated with an order, explaining a status change, identifying an adjustment, and determining how current the data are. Each decision implies a data requirement.
Avoid beginning with a long list of desirable columns. A field is useful when it supports a defined question. Asking for every available detail can increase complexity and data exposure without improving the merchant’s ability to operate the program.
In a fictional Shopify pilot, the merchant needs to connect order references to awards, identify which records changed since the previous report, and understand whether a total includes pending activity. The provider supplies a sanitized export with sample references rather than real recipient details.
RebateCardX’s reporting overview provides a starting point for discussing available report categories. The sample review should confirm the actual approved program scope instead of assuming every desired field is included because reporting is mentioned publicly.
Inspect a sanitized sample against required fields
Use a rubric that records what the sample demonstrates and what remains unanswered. The fictional field names below are descriptive examples, not a RebateCardX API or export schema.
| Required decision | Sample evidence to inspect | Fictional observation | Acceptance consequence |
|---|---|---|---|
| Connect an award to the relevant purchase | Stable order and award references with a documented relationship | Both references present in the sample | Verify whether the mapping covers the proposed workflow |
| Explain current status | Defined status vocabulary | Status label present; meaning of “processed” unclear | Request a definition before accepting the field |
| Understand when an event happened | Event date and its meaning | Date supplied without time zone | Clarify interpretation and relevant precision |
| Identify a later correction | Adjustment or version relationship | Changed record appears without a reason or predecessor | Determine whether another approved report supplies the history |
| Know report freshness | Cutoff or last-complete-update information | File generation time supplied only | Ask whether generation time equals data completeness |
| Export the expected scope | Documented filters, limits, and delivery method | Sample contains one campaign only | Confirm multi-period and campaign scope before relying on it |
Inspect the sample as a user would. Select a fictional order and ask the analyst to explain the related award. Select a changed record and ask operations to identify what changed. If the answer requires assumptions not present in the definitions, record the gap.
Shopify’s reporting guidance can help establish the source-side business definitions used in the comparison. A provider export still needs its own field meanings and mapping; similarly named amounts or dates are not automatically equivalent.
A difficult case is a report that overwrites status history. A current-state export may be sufficient for one decision but insufficient for explaining a past adjustment. Do not reject it automatically or pretend it serves both purposes. Identify the missing decision and ask whether a permitted alternative record fills that gap.
Record missing data and acceptable alternatives
Classify each gap by its effect on the merchant’s work. A missing optional display label may be acceptable. An absent identifier that prevents connecting rewards to purchases can be material. The acceptance decision should explain the consequence rather than assign every field the same priority.
Request definitions in writing for ambiguous terms. “Issued,” “delivered,” “claimed,” and “spent” describe different events unless the provider explicitly defines them otherwise. A report should not be accepted on the assumption that the merchant’s preferred meaning matches the provider’s label.
Check timing with a concrete scenario. If an event occurs late in one day and appears in the next file, which date will the report show? Is the export a snapshot, a list of changes, or a cumulative record? The answer affects how the merchant will use the data even before any live reconciliation begins.
Confirm export scope and continuity. Ask whether the merchant can obtain the required historical periods, how corrections appear, what permitted limits apply, and what happens to access at the end of the relationship. Do not infer an unlimited export right from the presence of a download button in a demonstration.
Use a small acceptance record: requirement, observed sample, supporting definition, gap, acceptable alternative, decision owner, and final status. “Accepted with alternative report B for adjustment history” is more precise than “reporting looks good.”
Do not request real card data to make the sample realistic. Synthetic references and representative status changes can demonstrate structure without exposing sensitive credentials. If the sample contains personal data unexpectedly, use the approved handling route and request an appropriately sanitized version for wider review.
For the fictional pilot, procurement remains open on the ambiguous processed status and adjustment history until the provider supplies definitions or an acceptable alternative. The stable identifiers are promising evidence, but they do not close every reporting requirement by themselves.
The finished rubric shows exactly what the merchant can decide from the proposed reports and what it cannot. That turns a broad sales feature into a verifiable capability, reducing the chance that the team discovers a missing identifier or unexplained status only after real customer work depends on it.
Discuss which reports and sample data can be reviewed for your proposed Rebate Card X program. Discuss program fit.
Source references
This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.
