In-house storefront launch · G.M. Treble
Pumpify
Launch of a second branded storefront inside an existing Magento 2 installation, with a large catalogue content project behind it.
eCommerce
Product data and feed management
Product data and feed management is the maintenance of the data behind your catalogue: attributes, imports, validation and the feeds that send products to Shopping and marketplaces. It suits businesses whose catalogue is too large to manage by hand and whose feeds keep rejecting products.
When this helps
Problems this solves
- Supplier files in a different structure every time they arrive.
- Merchant Center disapprovals that nobody has worked through.
- Attributes stored inconsistently, so filters and feeds cannot use them.
- The same product data maintained separately in three systems.
Scope
What's included
Every quote lists the deliverables in writing, so there is no ambiguity about what you receive.
Deliverables
- Attribute model and field mapping from your sources to the target platform.
- Import routines and templates, with validation rules that catch bad data before it lands.
- Catalogue import execution in controlled batches, with sample verification.
- Shopping and marketplace feed setup, including required fields and category mapping.
- Disapproval and error resolution, with the recurring causes fixed rather than patched.
- A repeatable workflow document so updates do not depend on memory.
Not included as standard
- Missing source specifications cannot be invented; gaps are reported as gaps.
- Feed platform approval decisions rest with Google, Amazon, eBay or the channel.
- Writing descriptions is separate work, covered by the content services.
Anything here can be added to the scope and priced separately.
Defined starting point
Product data project
Fixed price after scoping
Typically includes
- Review of a representative sample and target requirements
- Agreed field mapping and validation rules
- A sample batch to establish structure
- Processing and checking of the agreed catalogue
- Import-ready files, or an agreed import
- Post-import sample check and handover notes
Process
How the work runs
Step 1
Sample
Examine real source data and the destination's requirements.
Step 2
Map
Agree fields, units, validation rules and output format.
Step 3
Process
Run the catalogue in batches with checks between them.
Step 4
Hand over
Supply files or import, verify a sample and document the workflow.
What I need from you
- A representative sample of source data, including the messy examples.
- Platform and channel access.
- Decisions on units, naming conventions and mandatory fields.
What changes the price
- SKU and variant count.
- Number and quality of source files.
- Number of output channels and their field requirements.
- Whether the work is one-off or an ongoing workflow.
Experience
Relevant background
Relevant experience includes a catalogue content project covering 26,000 SKUs, built from supplier material and specifications extracted from more than 4,000 pump datasheets.
Questions
Frequently asked questions
Related
You may also need
Product descriptions & catalogue content
Product descriptions, short descriptions, technical attributes, category content, metadata and import-ready outputs at agreed catalogue scale.
Read moreeBay listing creation & management
New and existing listings, titles, item specifics, variations, image and content preparation, catalogue connections, pricing and ongoing management.
Read moreAPI & CRM integrations
Connect websites and business systems, including HubSpot, Sage and WooCommerce, with agreed mapping, error handling and monitoring.
Read moreGet a fixed cost for product data & feed management.
Share a little about your website, your goals and what is getting in the way. I'll use that to work out the right scope and next step.