Supplement Product Records: Connect the Catalog, Supplier and Order

By NUMUS editorial team

A useful product record lets another person follow the same item from your storefront to its supplier record and a completed order. It answers a practical question: can you explain what was offered, what was sourced and what was sent without guessing which document belongs to which product?

This guide builds one worked trace. It is an organizational exercise for a processing conversation, not a statement that every provider requires these documents. It does not establish product safety, health benefits or eligibility for payment processing. For the broader business context, see supplement payment processing.

Start with the item the customer actually sees

Choose one active product and one specific variant. Record its storefront name, internal identifier, package size, current page address and the date you checked the listing. Include any bundle contents that affect what arrives. A generic category such as “vitamins” does not identify the item in a particular order.

Stripe's website checklist asks businesses using Stripe to describe their products clearly and explain applicable fulfillment policies. That provider guidance is a useful reason to compare a saved listing with the actual offer; it does not establish which supplements Stripe or another provider will accept. Stripe: Website checklist.

Use identifiers your team can reproduce consistently. Shopify describes SKUs as internal inventory and sales identifiers, distinguishes them from barcodes, and recommends unique SKUs for product variants. Its guidance does not make a particular SKU format an underwriting requirement. Shopify: Using SKUs to manage inventory.

Worked example: one bottle, six linked records

Everything in this example is fictional. Fieldglass Supplement Store sells “Catalog Item A,” one 60-count bottle, under merchant SKU FGS-A60. The names, dates and records below illustrate an internal filing method. They are not sample certification, a bank checklist or evidence about a real product.

The trace follows a chain: listing version → merchant SKU → supplier item → receipt → customer order → shipment. Each arrow needs an identifiable record or an explicitly marked gap. A supplier invoice alone cannot explain what a customer saw on the product page.

Notice the distinction between the supplier and manufacturer. In this example, SUP-17 identifies the business that sold inventory to Fieldglass. It does not automatically answer who manufactured it. That unanswered field stays “not confirmed,” with a named person responsible for asking.

The supplier correspondence was also necessary because INV-118 used SUP-A-60 rather than FGS-A60. Before MAP-08 arrived, the purchasing lead could propose a match but could not mark it confirmed. The dated reply closes that specific identification gap; it does not certify the product.

Bring an outline of the records you have and the gaps you found. Discuss your product and supplier records.

Keep the record useful when something changes

Suppose the fictional supplier announces a packaging change on October 20. The catalog manager should be able to determine which listing described FG-204 without replacing its history with today's version. Use a small change log:

1. Describe the change. Record who reported it, when, and which item identifiers it affects. Separate a packaging update from an unconfirmed change to the product itself.
2. Identify affected records. List the current storefront version, supplier reference, incoming inventory and open orders that need comparison.
3. Record the unresolved question. For example: “Does the incoming shipment still match the package count shown to customers?” Assign an owner and follow-up date.
4. Document the decision. Record which listing or fulfillment instruction changes, who approved that operational change, and when it takes effect.
5. Keep earlier orders traceable. Link FG-204 to its original offer and dispatch record. Link later orders to the version actually used for them.

This is a suggested working method. It does not determine whether a changed product can be sold or processed. If a change affects the business description given to your provider, ask what information it needs before relying on an earlier review.

Use a gap log instead of a complete-looking folder

For each missing link, write four things: the question, the current evidence, the responsible person and the next action. “Supplier asked October 21; awaiting reply” is more useful than an empty cell or an unsupported “verified” label.

Check that a shipment reference belongs to the same order and item. Stripe's illustrative dispute evidence guidance, for example, lists relevant carrier, shipping date, delivery date, tracking and status information for physical-product nonreceipt cases. That is a provider-specific evidence example, not a promise that any collection of records will resolve a dispute. Stripe: Dispute sample evidence packets.

Keep the working trace concise enough that a colleague can follow it. Store source records in your normal controlled systems, and use references in the summary. Avoid copying customer payment credentials into a catalog worksheet.

Turn the trace into questions for review

Ask the reviewing provider which product and supplier records are relevant to your actual catalog, which date or version it needs, and how to supply requested material. Clarify whether it wants a representative example or broader coverage. Do not present one complete trace as proof that every item is documented.

Also ask how to report changes to suppliers, products or fulfillment arrangements. Our high-risk merchant account overview provides context for discussing the business model; the provider's response determines the next information request.

You can begin with a plain description of the catalog, the records available and the questions still open. Discuss your product and supplier records.