Sec. 01 — Overview · for the eCommerce Database Manager role
A 104,000-product catalog is only as good as its worst record.
I sampled JB Tools' live search feed and product pages. In a 799-item slice I found double-encoded characters in product names that carry through to titles and JSON-LD, UPCs printed on the page but missing from the schema, percent-encoded schema descriptions, inconsistent attribute casing, and a torque-wrench category that is a third out of stock while sold-out items still rank in search. This is a four-page walkthrough of the defects, a working triage board, and the supplier-price SOP I'd run as your Database Manager.
What this role owns
“Manage and maintain our catalog of tens of thousands of products across hundreds of suppliers… pricing, UPCs, SKUs, weights, dimensions, descriptions, images, specifications… supplier spreadsheets and large datasets… Excel/Google Sheets and AI tools.”
That is the job I've done: 14,000+ SKUs migrated and maintained by CSV, attribute mapping and QA.
Defects reach the shopper & the feed
Encoding artifacts show up in SERP titles. A missing gtin blocks clean Google Merchant Center matching. A sold-out item at #3 in search is a dead end at the top of results — the kind of thing behind the BBB complaint mix (Product 15 of 50).
Census → fix → prevent
A full-catalog defect census, a fix-priority board weighted by price and stock, a schema patch that reaches every product at once, a sold-out policy, and a supplier price-change intake so a price file becomes a validated import — not a manual afternoon.