How to Structure a Pricing Ops Team for Marketplace Scale

Pricing operations is one of the most under-resourced functions in ecommerce. Most companies either have no dedicated pricing team (pricing decisions are made ad hoc by category managers) or a pricing team that's drowning in manual work they've never been given tools to automate. Neither model scales.

The three core pricing ops roles

Pricing Strategist: Sets the positioning logic — what margin targets look like by category, how aggressively to compete on different product tiers, how to respond to specific competitive scenarios. This is a thinking role, not an execution role. One strong strategist can cover a very large catalog with the right infrastructure.

Pricing Analyst: Owns the data layer — monitors rule performance, runs weekly audits on outlier decisions, maintains cost data accuracy, and flags competitive moves that need strategic review. In a mature setup, most of this is automated alert-based work, not manual analysis.

Rule Engineer (or the analyst wearing a second hat): Builds and maintains the rule library. Translates strategic positioning into specific rule logic. Tests rules in review mode before promotion to automation. This role requires comfort with conditional logic and attention to edge cases, but not engineering skills.

What this looks like at different scales

Under 5,000 SKUs: one person can combine all three roles, supported by a good repricing platform. 5,000–25,000 SKUs: strategist + analyst, with rule-building shared between them. 25,000+ SKUs: dedicated strategist, two analysts, and a rule engineer. Enterprise catalogs (100K+ SKUs) may add channel-specific analysts per marketplace.

The common failure mode

Pricing ops fails when it becomes entirely reactive — constantly firefighting bad decisions instead of improving the system that produces them. The fix is ruthless prioritization: spend 70% of team time on rule improvement and cost data maintenance, and 30% reviewing decision output. Most teams have this inverted.