How to Vet a Digital Goods Supplier: A Reseller Guide

Choosing the wrong supplier for digital goods costs more than margin — it costs your store's reputation. A buyer who redeems a code that returns an already-used error does not wait for your resolution process; they open a dispute and warn their network. As a reseller, your name is on that transaction, not the supplier's. Supplier vetting is therefore not a one-time due-diligence step: it is an ongoing operational discipline that determines whether your business survives its first hundred orders or its first hundred thousand.

Why Provenance Is the First Filter

The digital goods supply chain is opaque by design. Gift card codes can travel through four or five hands before reaching you, and each step is a potential point of compromise — resold codes, platform-recalled batches, or inventory sourced through a compromised promotional channel. Asking where a code originates is not paranoia; it is the foundational due-diligence question every serious buyer must ask first.

A credible supplier will give you a direct, specific answer about source channels — authorized reseller relationships, platform APIs, licensed distribution agreements — not a vague reference to official channels. An evasive answer is a disqualifying signal.

FazerCards publishes its supplier vetting standards openly: provenance verification, a documented test period for each new source, and ongoing monitoring. When evaluating a wholesale platform, asking whether they publish their sourcing standards is a fast way to separate platforms that have done this work from those that have not.

The Four Pillars of a Trustworthy Supplier

1. Provenance and Source Transparency

The supplier can describe the type of source channel — licensed distributor, platform partner, authorized regional reseller — not necessarily the specific vendor name, but the category and structure.
The supplier maintains documented anti-fraud sourcing policies, not just verbal assurances.
The supplier separates codes sourced from gray-market channels from platform-official inventory and prices them accordingly.

How to verify: Request a sample of 10 to 20 codes across different denominations and redeem them on a test account before placing any volume order. A compromised batch almost always produces failures that cluster by denomination or region. Random single failures are noise; clustered failures signal a sourcing problem.

2. Fulfillment Reliability and Delivery Speed

For most categories, instant or near-instant delivery — under 60 seconds — is the baseline expectation. A platform that routinely takes hours is not using an automated inventory pipeline.
Ask whether the supplier publishes an SLA and a status page. A platform with no observable uptime history has not yet been tested under real load.
Run a few test orders at 10 to 50 units across your target SKUs during non-peak hours. If the platform shows out-of-stock on standard denominations within minutes, inventory depth is thin.

How to verify: Use webhook delivery events during your test period to log the exact fulfillment timestamp on each order. A supplier that passes a manual spot-check but fails under sustained load shows clearly in delivery-timestamp data. Logging every fulfillment event from day one gives you an auditable trail — essential if a dispute arises later.

3. Financial Terms and Pricing Transparency

Does the platform publish prices before you commit funds? Opaque pricing is a negotiating disadvantage you should not accept at the start of a new supplier relationship.
Understand whether your capital locks on deposit. A deposit model with a slow or complex withdrawal process is a cash-flow risk.
Determine whether margin improvements are tied to volume or to a fixed plan. Volume tiers favor single large buyers; plan-based tiers — see Bronze, Silver, and Gold plans — let you predict margin from day one regardless of individual order size.

How to verify: Review published pricing before committing any funds. Place a small first order and confirm the invoiced amount matches the published price. A fee surprise in the first order tells you how the relationship will be managed throughout.

4. Dispute and Replacement Handling

This is where most supplier relationships collapse. What tests a supplier is not a perfect order; it is an order where something goes wrong. Three scenarios to evaluate before committing volume:

Code redeemed before delivery: the buyer gets an activation error — the code was already used. The supplier must replace or refund within a defined SLA, ideally within four hours.
Valid code, wrong region: the code is real but region-locked to a market the buyer cannot use. This is a sourcing mismatch, not user error, and the supplier should own the resolution.
Batch invalidation: a block of codes is recalled by the platform for fraud reasons after you have already delivered them to your customers.

How to verify: Ask the supplier's support team to explain the replacement policy for each of these scenarios before you commit significant volume. The speed and specificity of the answer tells you more than any policy document. A support team that routes your scenario question to a generic FAQ has not built real dispute resolution infrastructure.

Red Flags That Signal a Risky Supplier

Prices materially below market with no disclosed explanation. Below-market pricing can be legitimate, but only when the source and reason are transparent. Undisclosed pricing hides the risk inside the price.
No published SLA, no status page, and a single email as the only support contact.
Bulk orders require full upfront payment with no partial-delivery or escrow option.
The replacement policy requires you to collect end-customer evidence — chat logs, screenshots, or video of a failed redemption. This shifts your burden of proof to a standard that is usually impossible to meet.
No API or webhook capability. Manual delivery pipelines do not scale and produce no auditable record for dispute resolution.

How to Run a Structured Test Period

A structured test period — not a single sample order — converts a one-time luck check into an operational decision:

Define the test scope. Select 5 to 10 SKUs across the product categories you plan to sell. Include at least one high-velocity SKU and one edge case such as a regional variant or a large denomination.
Set a volume floor. Run at least 50 orders across the test SKUs over 5 to 7 days. You are testing inventory depth and consistency, not a single batch.
Log every delivery timestamp. Use webhook events or API polling to record exact fulfillment times. Calculate the 95th-percentile delivery time — it is more meaningful than the average.
Simulate a dispute. Submit one test dispute and inform the supplier in advance that it is a test. Measure time to resolution and quality of the replacement.
Check for batch correlation in failures. If 3 of your 50 test orders fail, determine whether they share the same SKU, denomination, or date. Clustered failures reveal sourcing problems; isolated failures are acceptable noise.
Evaluate support responsiveness. Track time-to-first-response and time-to-resolution across any support tickets opened during the test period.

Implementation Checklist

Ask the supplier to describe their source channels specifically — reject any evasive or generic answer.
Confirm the supplier publishes sourcing standards; see FazerCards supplier standards as a reference for what transparency looks like.
Request 10 to 20 sample codes across denominations and redeem them on a test account before placing volume orders.
Verify that published pricing matches invoiced amounts in your first paid order.
Review the dispute replacement policy in writing, covering each failure scenario specifically, not just in general terms.
Configure webhook or API logging for delivery timestamps from the first day of your test period.
Run a structured 5 to 7 day test across at least 50 orders before scaling to production volume.
Simulate a support ticket or dispute during the test period to evaluate response quality under low-stakes conditions.

FAQ

How long should I run a test period before scaling volume?

Five to seven business days and at least 50 orders is the minimum for standard categories. For high-value products such as large-denomination gift cards or premium subscription codes, extend the test to 14 days and add a deliberate dispute simulation before scaling.

What if the supplier refuses to answer scenario-specific dispute questions?

Treat it as a disqualifying signal. A supplier with a real replacement policy can explain it in concrete terms. Vague or redirected answers indicate either that the policy does not exist in practice or that the support team has never applied it.

Can I source from multiple suppliers through one storefront?

Yes, and many resellers do this to maintain inventory depth across SKUs. The risk is quality fragmentation — each supplier has a different reliability profile. Log fulfillment events per supplier from day one so that when failures appear you can trace them to the source. Read wholesale API and webhooks explained for how to build an auditable fulfillment layer across multiple sources.

How does buying through a vetted platform reduce sourcing risk?

A vetted wholesale platform performs supplier evaluation on your behalf — it maintains supply relationships, monitors code validity, and handles first-level dispute resolution. Your risk narrows from whether the original source provided a valid code to whether the platform fulfilled your order correctly. Start with the free 5-day Gold trial to evaluate the catalog and delivery pipeline before committing capital. See the B2B digital goods platform guide for a broader look at what to expect from a wholesale reseller platform.