What you receive
- One prepared product-and-variant file for one confirmed destination template.
- Up to 20 supplied fields total—including titles, SKUs, parent identifiers, and up to three option fields—made consistent under the approved rules.
- A validation and exception report listing missing facts, duplicate identifiers, conflicting options, and rows held for your decision.
- One consolidated in-scope preference revision.
Price and scope
$59 USD covers one flat supplier CSV file or one XLSX worksheet with up to 100 total product and variant rows, up to 20 supplied fields total including up to three option fields, one supplied target template, and one preference revision. The option fields are part of the 20-field limit, not additional fields. A variant row is one sellable option combination, and both product and variant rows count toward the 100-row limit.
The package prepares the file for review. It does not publish, import, or update products. Additional files or templates, more rows or fields, relationship reconstruction, complex bundles, research, images, copywriting, and live catalog work are quoted separately.
Need a working storefront as well as prepared product data? E-commerce development can include agreed catalog setup, checkout integration, testing, and launch under a separate written quote.
What to provide
- One authorized supplier file and the exact destination template or import specification.
- Confirmed product facts, prices, SKU and parent rules, option definitions, and any approved image links already present in the data.
- One reviewer for missing specifications, duplicate SKUs, and ambiguous parent/variant relationships.
Describe the source before sharing it. Do not include customer, order, payment, or account-access data that is not needed for catalog preparation.
From supplier file to review-ready catalog file
- Confirm the source, target template, accepted fields, option rules, identifiers, and reviewer.
- Map and format the supplied facts under the approved rules while preserving the source.
- Validate required fields, SKUs, parent/variant relationships, and option combinations.
- Deliver the prepared file and exceptions for your review and the included revision.
How the work is checked
- Account for every source row and check the required target fields.
- Check SKU uniqueness, parent identifiers, allowed option combinations, and row counts.
- Set aside rows with missing or conflicting facts instead of inventing product information.
What is outside this package
Invented specifications, product research, copywriting, translation, pricing strategy, image editing or licensing, SEO guarantees, inventory synchronization, existing-product updates, live imports, and publication are excluded. A prepared file is not proof that an untested store configuration will accept it.
See a catalog example
The EPA vehicle catalog preserves distinct configurations, separates incompatible measurement units, and records unresolved source values. Inspect the full source, prepared workbook, and change log.
Start with the headers and representative variants
Tell us the target platform, approximate row and field counts, and how many option fields the products use. We confirm fit against the target template before any private transfer. You review and approve the prepared file before paying; your team controls import and publication.
Clear scope. Careful checks.