Inventory import workbench
Help sellers bring in larger catalogs with field mapping, quality repair, category routing, team review, and controlled publishing.
Review every row state before the batch goes live
The import workbench separates rows that can publish from rows that need proof, duplicate review, policy review, draft cleanup, or hub intake.
Repair prompts change by category
The same CSV import can produce different repair prompts depending on what the buyer needs to trust the item.
Column Mapping
- Seller columns map to title, category, price, quantity, condition, photos, fulfillment, return setting, and item specifics.
- Category templates fill required fields for cards, GPUs, sneakers, retro games, art, books, auto, garden, home, and pickup.
- Mapping presets let repeat sellers reuse clean import rules.
Error Repair
- Rows flag missing cert photos, serial proof, measurements, fitment, condition notes, restricted terms, and weak titles.
- Repair actions can apply to one row, a filtered group, or a full batch.
- Blocked rows stay out of search, auctions, timed drops, and seller growth placement.
Team Review
- Owner, listing manager, photographer, pricing lead, and hub coordinator roles can review different steps.
- Approval notes explain who changed price, category, photos, hub routing, and publish status.
- Seller teams need role limits before a high-volume batch can go live.
Hub Routing
- High-value, fragile, bulky, or proof-light items can route to hub intake before publishing.
- Hub routing attaches intake checklist, photo needs, packing notes, and pickup or shipment preference.
- Local event items can move from import repair into timed-drop review.
Publish Controls
- Publish ready rows, save repair rows, schedule auctions, stagger fresh listings, or send qualified items to timed drops.
- Bulk edits can adjust price, reserve, quantity, pickup choice, return setting, and offer threshold.
- Every publish action should leave a clear audit note for the seller team.
Current Boundary
- This route shows the import workflow without accepting file uploads or storing seller files.
- Launch-ready commerce needs import storage, media processing, retry handling, permissions, recovery, and seller notices.
- Large sellers should see exactly why rows are ready, blocked, or routed to review.
Migration Readiness
Seller mapping, inventory mapping, policy mapping, records, redirects, support continuity, and cutover gates.
Bulk Listing
Templates, batch drafts, quality checks, and bulk actions.
Business Seller
Team review, approval gates, bulk publish limits, finance controls, and seller ownership.
Catalog Quality
Required attributes, variants, duplicate checks, proof rules, and listing repair.
Seller Workspace
Inventory, offers, auctions, orders, reports, returns, and analytics.
Seller Inventory
SKU rows, variant groups, quantity states, hub routing, relist paths, and repair work.
Seller Automation Rules
Convert imported inventory into reviewed relist, price, offer, alert, and hub routing rules.
Seller Growth
Placement, quality fixes, saved-search demand, and timed-drop candidates.
Item Checks
Category proof, condition notes, serials, certificates, and hub intake.
Current demo state
Import flow without file storage.
The demo shows mapping, repair, team review, hub routing, and publish controls without accepting or storing uploaded seller files.
Future platform state
Live import requirements.
Launch-ready commerce needs file storage, media processing, validation jobs, retry recovery, role permissions, seller notices, and publish audit history.
