Shopify product reference
- Shopify product title: [title]
- SKU and variant: [available SKU / variant]
- Barcode: [available barcode]
- Supplier model or catalogue reference: [reference]
Reusable supplier request
Supplier information request template for Shopify and Amazon
Use this email and question bank to ask a supplier for information about clearly identified products. Select the questions your team needs, replace the placeholders, and review the response before using it.
Content reviewed:
This template helps structure a conversation. Every question is optional until you decide it is relevant to the product, sales channel and market. It is not a universal legal checklist or a statement that a product is compliant.
Before sending
Prepare a request the supplier can answer
Confirm the business contact
Choose a supplier contact who can obtain the product records. Identify your company, the requester and the person who will handle follow-up.
List the exact products and variants
Match your product references to the supplier’s model or catalogue references. Separate variants if their materials, warnings or documents differ.
Choose the information and evidence
Remove irrelevant questions. Name the documents you need and explain the intended market, language and use of the response.
Set the response and review process
Add a realistic response date, a request link or reply instructions, and a reviewer. Check that the link remains available through the response period.
Product references
Make the product unambiguous for each sales channel
Include the identifiers you actually have and add the supplier’s own model reference where useful. A supplier may recognise its catalogue number more readily than your storefront title.
Amazon listing reference
- Amazon product/listing title: [title]
- ASIN: [available ASIN]
- Seller SKU: [available seller SKU]
- Barcode or product identifier: [available identifier]
- Marketplace: [marketplace]
- Supplier model or catalogue reference: [reference]
You do not need every identifier. The goal is to establish which product, model, variant and market each answer or document covers.
Copy and adapt
Supplier email template
Replace every bracketed placeholder and delete questions that do not apply. If you use a private request link, share it only with the intended supplier contact.
The complete email is visible below and can also be selected and copied manually.
Subject: Product information request – [Product / SKU / ASIN] Hello [Supplier contact], I am [Name / role] from [Merchant company]. We are preparing or reviewing our product information for [sales channel / marketplace / market] and need your help with the products supplied by [Supplier company]. Products concerned: - [Product title, model and variant] - [Shopify SKU / Amazon seller SKU / ASIN / barcode, where available] - [Supplier model or catalogue reference] Please respond by [Date] using [Private request link / reply instructions]. Answer separately for each product or model and explain which variants each answer covers. Please provide the selected information below: 1. Product identification and confirmation that it matches your supplied model. 2. Manufacturer name and relevant postal and electronic contact details. 3. Responsible-party details and role, where relevant to this product and market. 4. Product-specific warnings, safety information and instructions in [Language]. 5. [Named supporting documents requested], identifying the product/model covered and any issue date, version or expiry date shown. 6. [Other selected product questions]. If information is unavailable or does not apply, say so and explain the reason. Please do not guess. Identify the source of the information and flag any change from previously supplied records. Name each document clearly and state which product/model it covers. If the response date cannot be met, contact [Merchant contact] with the missing items and an expected follow-up date. We will review the response and contact you if clarification or a replacement is needed. Thank you, [Name / role] [Merchant company] [Business contact details]
Optional question bank
Choose questions for this product and request
These are preparation prompts, not claims about what every product requires. Adapt them to supported request fields, an available custom profile or your own supplier email. Keep factual answers separate from supporting files.
Product identification
- Which manufacturer model, catalogue number and variants match our references?
- Which supplied products or batches does this answer cover, and are any variants excluded?
- Have the model, materials or product identifiers changed since the previous response?
Manufacturer information
- What is the manufacturer’s name or registered trade name for this product?
- What postal and electronic contact details are relevant to this manufacturer?
- Where did these details come from, and when were they last checked?
Responsible party, where relevant
- Where relevant, which EU-based responsible economic operator is identified for this product?
- What are its name, role, postal and electronic contact details?
- Which products and markets does this role cover, and what record supports that relationship?
Warnings and safety information
- Which warnings, hazards, restrictions or safety information accompany this exact model?
- Which languages and product variants do the supplied warnings cover?
- Do the wording and identifiers match the current label, packaging and instructions?
Instructions
- Which use, assembly, handling, storage or care instructions apply to this model?
- Can you provide the current text or manual in the requested language?
- Which revision is current, and have any instructions changed?
Supporting documents
- Can you provide the named documents selected for this request, such as a manual, declaration, test report, safety data sheet or label image where relevant?
- Who issued each file, and which product/model does it cover?
- Are pages, annexes or referenced files missing from the supplied copy?
Document dates, versions and coverage
- What issue date, version and expiry date, if any, appear in each document?
- Which models, variants, batches, languages or markets are included or excluded?
- Does this file replace an earlier version, and what changed?
Your own product questions
- Which extra factual details does our team need for this product or market?
- What source supports the answer, and which product does it concern?
- If you cannot answer now, who can clarify it and when should we follow up?
Request examples
Replace broad requests with answerable questions
Name the information you want
Too broad: Please send all compliance documents and confirm everything is compliant.
Clearer request: For [model / SKU], please provide the manufacturer contact details, current warnings in [language] and [named document]. State the product coverage and document version.
Separate product variants and missing answers
Too broad: Are these details the same for your entire range? Please reply urgently.
Clearer request: Please answer separately for [model A] and [model B] by [date]. Confirm which variants each answer covers. Mark unavailable information and give a follow-up date instead of guessing.
When the response arrives
Review the response before accepting or publishing it
A reply or uploaded file is a submission for review. Resolve conflicting references and missing details, record the merchant’s decision, and request corrections where needed. Acceptance in your workflow is not a certification of legal compliance.
Manage the process in ComplyDock
Keep the request, supplier response and review together
ComplyDock connects selected products or listing references to an assigned supplier and a private, expiring request link. Suppliers can answer without an account. Supported fields and documents stay connected to their submission and merchant review history.
Select the supported information your team intends to review. Use configurable, versioned profiles and custom questions where available for your workspace and plan; this question bank is broader than the standard request fields. Supported items can be accepted, rejected or returned with correction feedback.
In Shopify, supporting document uploads depend on the selected plan. Eligible approved fields can be deliberately published through the configured storefront workflow. Collection, approval and publication remain separate steps.
Amazon Open Beta: collection and review
Amazon uses a separate Seller Central-connected workspace. ComplyDock does not currently publish approved information to Amazon listings or submit it to Amazon compliance workflows. Complete Amazon-required submissions in Seller Central.
ComplyDock organises supplier information and review decisions. It does not determine applicable law, verify a supplier’s legal statements, authenticate documents, appoint a responsible person or guarantee product compliance. Decide which questions and evidence apply to your product and market, obtaining qualified advice when needed.