How to turn supplier documents into product listings
Turn supplier documents into product listings with traceable specs, clear SKU matches, and a draft import file checked against your store template.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a workflow to turn supplier documents into product listings is
To turn supplier documents into product listings, extract the facts for each item you sell, write the customer-facing copy, and map the fields to the store's import template. Keep a reference to the document and row behind every important value. That lets you check whether a size, pack, price, or included part applies to the exact product variant in the listing.
A catalog import can create new records or overwrite existing ones, depending on how the store matches them. Check which products you already sell and which fields you intend to change before preparing the product CSV, a plain text table whose fields are separated by commas. The result is a set of drafts for the catalog owner to review and an import candidate for eligible rows. Send regulated, safety, or certification claims to a qualified reviewer before approval.
What it does for the business
- Give merchandising a shorter path to reviewProduct descriptions from spec sheets let a merchandiser evaluate draft titles and feature bullets beside the evidence. They can spend review time on high-impact wording, conflicting variants, and missing information.
- Keep existing work when updating a rangeAn old-to-new view lets the catalog owner inspect each proposed change and preserve existing copy or store fields where the supplier provides no replacement. The owner can approve individual updates without revisiting unaffected records.
- Ask suppliers for the information that blocks a listingA gap list with exact items and fields helps the buyer request a missing dimension, a current pack price, or proof of image rights in one pass. A reply can be matched to the affected rows without reworking the entire batch.
- Carry product decisions into the next supplier revisionStable item keys and saved decisions let a team find which descriptions, prices, or specifications changed on the next run. Review can then focus on the proposed changes and their effect on the storefront.
How to build a workflow to turn supplier documents into product listings, step by step
Set the store target and source authority
A listing batch needs one target template and a clear source for each important field.
What to do
- Record the target store, environment, market, currency, and review cutoff. Get the current import template and read how it handles identifiers, variants, blank cells, updates, and draft status.
- List the supplier documents by issuer, revision, issue date, and effective period. Name the authoritative source for specifications, costs, images, and availability. Flag overlapping revisions whose precedence is unclear.
- Check the current product export for scope and age. Keep update status uncertain for products you cannot verify against current store evidence.
- Confirm who approves the selling price and which unit and tax basis the price represents. Record the wholesale price and suggested retail price separately from the price authorized for your store.
Why
A supplier can revise dimensions and prices on different schedules. A file name that looks newer can still contain prices for another market or a future effective date. Starting with the template and authoritative sources keeps the team from making a valid-looking import file filled with values for the wrong products or store.
Extract the facts for each sellable item
Every important value should lead back to a specific place in the source.
What to do
- Build a product ledger, a structured record of original and normalized values. Keep the supplier SKU and other identifiers as text to preserve leading zeros. Store the source file, page, table, row, and column for material attributes.
- Read multi-page tables with their headings, units, and footnotes. Check whether a value applies across rows before carrying it down. Look at the original page when scanned text could confuse a letter with a digit.
- Keep product family, variant, sellable unit, supplier case quantity, and minimum order quantity separate. Record the price unit, currency, tax basis, and effective date together.
- Map each image to its item and variant, and record the permission that covers reuse. Track stock evidence separately with the date and market it describes.
Why
A pack size or specification copied from the wrong line can change what the customer expects to receive. Exact source references help a reviewer check that the listing and price describe the same sellable unit. The original values also make it easier to correct a conversion without having to extract the documents again.
Draft the copy and classify each import row
A listing should only make claims supported for the exact item being sold.
What to do
- Write concise titles, descriptions, feature bullets, and image alt text from supported facts. Trace meaningful claims to the source and flag unverified supplier claims for internal review.
- Match to the current store IDs using the target's documented update rule. Label each row new, update, or possible duplicate. For updates, show the old and proposed values and select only the intended fields where the template allows it.
- Use the documented draft setting where supported. Keep ambiguous matches and rows lacking required values out of the candidate. Record which source or owner decision would resolve each gap.
- Write the file with the target's required column names and values. Check encoding, field lengths, variant relationships, quoting, and required fields. Use a CSV writer so commas and line breaks stay inside their intended cells.
Why
Closely related variants can share almost all their description while differing in a detail that determines suitability. Checking source claims at the item level protects that distinction. Matching against current records also gives the owner a chance to catch an unintended overwrite before an update appears in the store.
Review the source claims and the actual file
Review the file the store would receive and the evidence that supports it.
What to do
- Ask a second reviewer to check the required fields, conflicting variants, and material prices against the source pages. Route claims with legal or safety implications to a qualified reviewer.
- Read the finished file with a standard CSV reader and compare the parsed values to the ledger. Verify variant grouping, unique identifiers where required, draft flags, and the absence of withheld rows.
- Check untrusted text for formula-leading characters, including after leading whitespace. Use a documented literal representation that preserves the value, or withhold the affected content and keep the exact original in the ledger.
- Review how the target handles omitted columns and empty cells before approving an update. Verify which existing values each changed row would keep or overwrite.
Why
A file that parses can still carry the wrong pack quantity, an unsupported claim, or an empty value that replaces working store copy. Source review catches mistakes in the draft, while parsing the exact candidate catches mistakes introduced when exporting it. Both checks give the owner concrete evidence to review.
Hand off the drafts and remaining decisions
A handoff should make each unresolved item actionable.
What to do
- Give the catalog owner the drafts, candidate, and gap list with the exact target store and environment. Identify which variants are eligible, which are withheld, and the source behind each decision.
- Name what needs to be refreshed, including dated prices, availability, current store IDs, or image permission. Assign each gap to the person who can answer it.
- Keep approved copy versions and stable product identities for later supplier revisions. When a value changes, show the earlier and current evidence and reopen the affected decision.
Why
A catalog team needs to know what it can review now and who can advance the items waiting on a decision. A handoff tied to exact variants also gives the team a useful history when a future price list renames an item or omits a row.
Common mistakes
- Treating the supplier cost as the retail priceUse only a selling price or pricing rule approved for the target market and unit.
- Carrying values through an unclear page breakVerify the scope of headers and footnotes in the source before assigning a value to a variant.
- Dropping leading zeros from identifiersPreserve source identifiers as text through extraction and CSV validation.
- Assuming a blank cell preserves the old valueCheck your target's update rules and include fields only where the intended outcome is clear.
- Using supplier imagery without checking rightsRecord permission for the intended reuse and match each approved image to the correct item.
What a good result looks like
- A confirmed target template and store, with the market and review cutoff.
- A traceable source for every material product fact and approved selling price.
- A stable key for each sellable item and a documented match for each update.
- A candidate file reconciled to the ledger, with unresolved rows withheld.
- A gap list that states the question, exact variant, and person who can resolve it.
And then what? Using the result
- Send the supplier one request for missing facts, pack details, or rights, identified by the exact variant and document line.
- Ask the catalog owner to approve the intended changes, especially updates to existing copy, images, or prices.
- Refresh dated fields and verify a small set of approved rows in the store's review process before scheduling a wider import.
- File the reviewed drafts and source decisions with the stable item map so the next revision can be checked against them.
When to run it
- Adding a supplier rangeTrace each sellable variant to its supplier specifications, then resolve prices, image rights, and store-required fields before approving rows.
- Updating a live range from a revised price listUse the current export and exact matching rule to check which price fields would change and preserve other store content.
- Preparing products for a different store or marketCheck the new template, units, currency, and required attributes. Carry forward verified facts and obtain approvals for the new market's prices and claims.
Questions people ask
How do you turn supplier documents into product listings?
Extract variant facts with source references, draft the copy, match current store items, and map eligible rows to the actual target template. Give the owner a separate list of fields or decisions blocking the remaining rows.
How do you write product descriptions from spec sheets?
Write from confirmed facts about the exact sellable variant. Include details that help buyers choose, such as size or included pieces, and route unverified certification or safety claims to a qualified reviewer.
Can you use a supplier price list as your retail price?
Use a supplier price as the retail price only when the store owner has approved it for the correct sellable unit and market. Keep cost, suggested retail, and approved price in distinct fields.
How do you tell whether a product is new or an update?
Check the current store export against the target's documented match rule and verified product identifiers. Mark uncertain matches for review before creating a new record or overwriting an existing one.
What should you do when a required field is missing?
Record the field, affected variant, and the evidence or approval needed, and withhold the row from the import candidate. Keep supported draft copy available for review.
Does a valid product CSV mean the listings are ready to publish?
A valid product CSV shows that the candidate passed local file checks. The owner still needs to verify platform behavior, approve the content, and confirm publication settings before applying it.
More jobs in E-commerce
Turn supplier documents into product listings, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac