title: "50 Questions to Ask Before a Commerce Replatform"
slug: commerce-discovery-checklist
content_type: checklist
primary_keyword: commerce replatform checklist

50 Questions to Ask Before a Commerce Replatform

Summary

Most replatform discoveries ask surface-level questions and get surface-level answers. This checklist covers the questions that expose hidden complexity, misaligned expectations, and scope risks before they derail your project.

Surface-Level Questions Get Surface-Level Scope

The standard discovery checklist asks things like "What platform are you currently on?" and "What's your timeline?" These get answered in the first sales call. They don't tell you anything useful about scope, risk, or actual requirements.

The questions that matter are the ones stakeholders have to think about before answering. The ones that surface disagreements between departments. The ones that reveal undocumented workarounds, unstated assumptions, and business logic buried in custom code.

This list is organized by domain. Don't treat it as a linear questionnaire, use it to structure conversations across stakeholder groups and identify where you need deeper investigation.

Is the Replatform Solving the Right Problem?

What business capability are you unable to execute on your current platform that's driving this decision?
Which revenue stream is most at risk if this project is delayed by six months?
Are there planned business model changes (new channels, geographies, customer segments) in the next 18 months that the new platform must support?
What's the internal cost of maintaining the current platform annually, including workarounds, manual processes, and lost opportunity?
Who owns the P&L that this platform supports, and are they aligned on scope and timeline?
Has leadership agreed on whether this is a like-for-like migration or a business transformation?
What would a failed replatform cost the business, in revenue, reputation, and internal credibility?

What Technical Debt Are You Inheriting?

Most teams underestimate current-state complexity by 40–60%.

How much of your current platform's business logic lives in custom code versus configuration?
Which integrations are undocumented, and who maintains them?
Are there any "temporary" solutions that have been running in production for more than two years?
What percentage of your product catalog uses non-standard attributes or custom fields?
How many pricing rules, promotions, or discount structures are currently active, and how many are actually used?
Which parts of the checkout flow have been customized, and what drove those changes?
Are there any compliance or contractual constraints tied to your current platform or data residency?

Where Will Data Migration Blow Your Timeline?

Data migration is where most replatforms fail their schedule. These questions expose the real scope.

How many SKUs are active, and how many are in the system but inactive or obsolete?
What's the source of truth for product data, the platform, a PIM, an ERP, or spreadsheets?
Do you need to migrate historical orders, and if so, how far back and for what purpose?
How clean is your customer data, duplicates, incomplete records, invalid emails?
Are there customer segments or loyalty tiers that must be preserved with their history intact?
How much content lives in the CMS versus hardcoded in templates?
Who owns the taxonomy and categorization structure, and is it consistent across channels?
Are there SEO-critical URL structures that must be preserved or redirected?

Which Integrations Are Scope Bombs?

Every integration is a potential scope bomb. Map them early or pay later.

How many systems currently integrate with your commerce platform, including ones "managed by another team"?
Which integrations are synchronous and which are batch, and do you know why?
Are there any integrations running on deprecated APIs or unsupported middleware?
What happens to downstream systems if the commerce platform goes down for 30 minutes?
Which integration failures are currently handled manually, and by whom?
Are there any vendor contracts that constrain your integration approach or require specific protocols?
Do you have documentation for your current integration architecture, and when was it last updated?

Who Can Kill This Project?

Replatforms fail more often from stakeholder misalignment than from technical issues.

Which department has the most to lose if this project is delayed, and are they adequately represented?
Who has veto power over platform decisions, formally or informally?
Are there stakeholders who were excluded from previous platform decisions and still hold grudges?
Which team currently owns the most workarounds on the existing platform?
Is there agreement between marketing, operations, and IT on what "success" looks like?
Who will own the platform post-launch, and have they been involved in requirements gathering?
Are there stakeholders who believe this replatform will fail, and what's driving that belief?

What Will Operations Complain About Post-Launch?

Operations teams live with platform decisions daily. Their input predicts post-launch friction.

How many warehouse or fulfillment locations does the platform need to support, and are they on different systems?
What's the current process for inventory sync, and what's the acceptable latency?
Are there order routing rules that account for regional inventory, shipping cost, or delivery SLA?
How are returns processed today, and what's broken about it?
Which operational reports are generated from the commerce platform, and who relies on them?
Are there seasonal or promotional peaks that require specific operational modes?

Does Your Platform Choice Actually Fit?

If you're still evaluating platforms, these questions clarify decision criteria. If you've already selected, they validate fit.

What's the actual driver for considering a headless or composable architecture, flexibility, or because it sounds modern?
Are you prepared to own frontend development and deployment indefinitely, or do you need a managed storefront?
What's your build-versus-buy philosophy for commerce functionality, and is it consistent across leadership?
Which platform capabilities are genuine requirements versus nice-to-haves inherited from an RFP template?
Have you validated your integration requirements against the shortlisted platforms' actual API capabilities?
What's your plan if the selected platform doesn't support a critical capability out of the box?

Are Your Constraints Real or Invented?

Projects fail when constraints aren't explicit. These questions force clarity.

Is your go-live date driven by a real business event (contract expiration, peak season, fiscal year), or is it arbitrary?
What would you cut from scope if the project was trending 30% over budget at the midpoint?

How to Use This List

Don't send this as a form. Use it to structure discovery conversations, identify gaps in stakeholder coverage, and surface areas where you need deeper investigation.

The goal isn't to get answers to all 50 questions. It's to identify which questions expose real complexity, and to make sure those get answered before you commit to scope, timeline, or architecture.

Track the answers in a structured format. Link them to the decisions they inform. Reference them when scope creep shows up three months into delivery.

Turning Answers Into Architecture with DigitalStack

DigitalStack gives you a structured workspace to capture and connect discovery inputs across business, technical, stakeholder, data, and operations domains.

Stakeholder surveys let you gather input from multiple departments systematically, not through scattered email threads. The Discovery Canvas structures findings into a connected model: a business constraint captured in week one links directly to an architecture decision in week three. When you move to estimation, the data is already there, linked, not copy-pasted from a Google Doc you'll never find again.

The checklist tells you what to ask. DigitalStack is where the answers connect to decisions.

Next Step

Run your next commerce discovery in DigitalStack. Collect structured answers, orchestrate stakeholder input, and connect your findings directly to architecture and estimation.

Start your first engagement free →