Outsource
Catalog data management services
Catalog data management services: supplier price and stock updates, catalog audits, category upkeep and listing fixes in your store or PIM. $5/person-hour.
$5 per person-hour for standard tasks.
Catalog data management keeps product data correct after launch: prices and stock that match the supplier, categories that match your taxonomy, and listings that pass marketplace checks. Deepen AI runs it as a routine in your store admin, PIM or spreadsheets, with a named owner and a change log.
What the work is, and who buys it
Buyers are retailers and distributors with thousands of SKUs and many suppliers, sellers on several marketplaces, and brands whose PIM and storefront have drifted apart. The problem is rarely one big error. It is small drift: a supplier price change that was missed, a discontinued item still for sale, a category rename that was only half applied. Each one costs a little margin or creates a support ticket.
Many teams handle this with whoever has time that week. A managed routine replaces that with a named team lead, written rules and a log of every change. For building new listings from scratch, see ecommerce product data entry.
What our team does
- Apply supplier price and stock files on your schedule, and log every change
- Archive or deactivate discontinued SKUs, following your rule
- Reassign categories after a taxonomy change, and fix products filed in the wrong place
- Audit the catalog for missing attributes, broken images, duplicate SKUs and inconsistent units
- Fix suppressed or errored listings from marketplace reports
- Compare your PIM export with the live storefront and reconcile the differences
- Update seasonal collections, badges and sale flags on your dates
When an audit finds thin listings that need attributes filled, that work is product data enrichment, and the same team can take it on.
How it runs
- You share the routine. Tell us which files arrive, from whom and how often, plus your rules for price changes, discontinued items and stock-outs, your taxonomy, and accounts in the tools.
- We agree scope and train. Our ops team sets the people, hours and schedule in your pilot plan. Many teams start the pilot with a baseline audit, so the routine begins from a known list of problems. We build a gold set of past file updates with known-correct results for you to confirm.
- We deliver, with a named team lead and QA sampling. The team runs the routine. The team lead owns the change log and the decision list, and sends changes above your approval thresholds to your contact before applying them.
- You get a weekly report. Files applied, changes by type, audit findings, QA sample results and open questions.
Illustrative example: applying a weekly supplier file
Illustrative only. The supplier, SKUs and prices are invented.
- Input: supplier file dated 2026-09-28, 412 rows, compared with your live catalog
- Your rules: archive discontinued items, never delete · new SKUs go to the enrichment queue · price rises over 10.00 need approval
- Output, BR-2210: price 14.99 to 16.49, updated in the store and logged
- Output, BR-2214: discontinued by the supplier, archived, not deleted
- Output, BR-2187: stock 0 with restock date 2026-10-20, set to backorder with the date shown
- Output, BR-2301: not in your catalog, added to the enrichment queue, not created
- Output, BR-2290: price 41.00 to 58.00, held and sent to your contact for approval
- Output, change log: 5 rows changed, 407 rows checked with no change
- Who did what: one team member applied the file. A QA reviewer re-checked the five changed rows against the supplier file as part of the weekly sample.
How we keep the catalog accurate
Catalog work is only as good as its rules, so the team lead turns every new question into a written rule and adds it to the decision list. Gold examples from your past updates measure each person before and during live work. QA reviewers re-check a sample of applied changes against the source file, and a sample of audit findings against the live store. They do not re-check every change. The change log means any update can be traced to a file, a date and a person. The weekly report shows the acceptance rate on the sample and the error types found. See how we check quality.
Pricing scope
Catalog data management is a standard task at $5 per person-hour, with a named team lead and QA sampling included. Because the work is billed by the hour, a heavy week does not need a new agreement. Tell your team lead if a season needs more hours. Work starts with a two-week prepaid pilot: people × hours per week × 2 weeks × $5, with at least 20 hours per person per week. After the pilot, we invoice weekly in arrears. Catalogs in other languages, or technical products that need specialist knowledge, are quoted after our ops team reviews the task. See the pricing page.
When to use the enterprise team instead
If your product data comes from shelf cameras or store robots, and you need those frames labeled to train a product recognition model, that is computer vision annotation. The Deepen AI enterprise team scopes and prices it per project. See enterprise AI data services.
Send a recent supplier file and your rules for applying it. We email you a pilot plan with a quote.
FAQ
What do catalog data management services include?
Applying supplier price and stock files, archiving discontinued items, keeping categories in line with your taxonomy, auditing the catalog for gaps and duplicates, fixing listings that a marketplace has suppressed, and keeping your PIM and storefront in sync. Each change is logged.
What are virtual data entry services, and is this the same thing?
Virtual data entry usually means a remote person keying data into your systems. Catalog management is a managed version of that for product data: a trained team, a named team lead, written rules, QA sampling and a weekly change log, rather than one assistant working alone.
How often can you update our catalog?
On the schedule you set, such as daily, twice a week or weekly, within the hours in your pilot plan. If a season or sale needs more hours, tell your team lead.
Can you manage one catalog across several stores or marketplaces?
Yes. Tell us each channel in the pilot form. The team works on accounts you create in each one, and the weekly report shows changes by channel.
Do you delete products?
Only if your rules say so. Many teams prefer archiving to deleting, so history and reviews are kept. Either way, every change goes into the change log.