Identify the source edition and row unit
Record which supplier list or catalog version is being prepared and any printed effective date. Decide whether one row means a product, variant, pack option or price tier. A catalog line may contain several sizes, colors or quantities; those may need separate output rows under an agreed rule.
Preserve product identifiers exactly
Treat supplier codes and your own identifiers as distinct fields. Keep letters, leading zeros and meaningful punctuation. Do not replace a missing code with a description that happens to look unique. If the recipient needs a cross-reference to existing products, scope that matching task and the handling of unmatched items explicitly.
Make the unit and pack relationship visible
Record the printed unit, pack quantity and what the price applies to. A price per case cannot be compared directly with a price per single unit without additional confirmed information. Keep a derived unit price separate from the source price if the authorized workflow asks for that calculation. Document the formula and assumptions.
Handle tiers, currencies and notes deliberately
A single product may have different prices by quantity, customer group or effective period. Decide whether tiers become separate rows or a related table. Keep currency explicit and preserve notes that change the meaning of a price. Do not infer that a published product is currently available or that an older list remains valid.
- Source reference, edition and page or line
- Supplier product code and agreed variant fields
- Description, printed unit and pack quantity
- Printed price, currency and price basis
- Tier or minimum-quantity condition where provided
- Unresolved source or mapping questions
Review representative product patterns
Test the field map on ordinary products and the difficult cases: multiple variants, wrapped descriptions, missing units and tiered pricing. Reconcile output coverage against the source references. Check that a repeated header or subtotal has not become a product row. If source pages use different layouts, define the handling for each group before the full batch.
Deliver data for the next approved step
Agree whether the recipient needs a review workbook, a CSV matching an import template or both. Include field notes and unresolved exceptions. Preparing supplied product data does not publish store listings, update live inventory, scrape websites or decide selling prices. Those are separate actions for the authorized business.
A few useful answers
Can descriptions replace missing product codes?
Only under an explicitly agreed identification rule. Descriptions can repeat or change, so an unresolved code should remain visible.
Does a catalog price establish current availability?
No. Capture the source edition and stated facts. Inventory and current commercial terms require their own authoritative confirmation.
Can you import the finished list into our store?
The initial service prepares agreed files from supplied sources. Direct store access, publishing and automated synchronization are outside that deliverable.