Start here
Define the job before comparing the tools
Ecommerce stacks grow one urgent problem at a time. A returns app arrives after a bad week. A connector is added for a new marketplace. A former employee still owns an automation. Nobody means to create duplicate customer lists or three tools that send tracking messages, but that is how the stack becomes hard to trust.
Audit the workflow, not only the invoices. Follow one product, order, payment, shipment, refund, customer, and accounting entry through the business. Record where data starts, where it changes, where it gets stuck, and who notices when a connection fails.
The starting point
Create one inventory with the product name, business job, owner, administrator, renewal date, normal cost, data held, connections, users, and recovery method. If a tool has no owner, make that the first finding rather than guessing at its value.
The process
Work through the decision in a sensible order
Inventory tools and contracts
Use card statements, accounts-payable records, app stores, browser extensions, single sign-on, API credentials, and staff interviews. Do not assume the official software list is complete.
- • Vendor and product
- • Owner and administrator
- • Renewal and cancellation terms
- • Normal and peak cost
Follow the core records
Trace product, customer, order, inventory, payment, shipment, refund, and accounting data. Mark the owner of each field and every point where the same fact can be edited twice.
- • Source of truth
- • Update direction
- • Delay and failure alert
- • Manual correction path
Review use and duplication
Ask what work each tool completed in the last 90 days. A tool can be lightly used and still critical, so distinguish low frequency from low value.
- • Active users
- • Features actually used
- • Duplicate functions
- • Seasonal or emergency purpose
Review access and ownership
Remove former users, reduce administrator access, turn on MFA where supported, and move shared credentials or personal ownership into controlled business accounts.
- • Current user list
- • Admin and export rights
- • MFA and recovery
- • Service accounts and API keys
Test continuity and exit
Confirm exports, backups, restore steps, vendor support, and the business process used during an outage. A subscription is not a backup by itself.
- • Recent export or backup
- • Restore or replay test
- • Offline work procedure
- • Deletion and retention plan
Make four decisions
Every tool should end as keep, fix, replace, or retire. Record the reason, owner, due date, and safety step. Avoid turning the audit into a large simultaneous migration program.
- • Business outcome
- • Next action
- • Owner and date
- • Dependency and rollback
Owner worksheet
Write down these decisions
| Item | What to record |
|---|---|
| Keep | The tool has a clear owner, useful outcome, acceptable cost, controlled access, and a recovery path. |
| Fix | The tool still fits, but data, permissions, configuration, contract, documentation, or monitoring needs repair. |
| Replace | The workflow matters, but the current product no longer meets a defined need after a measured comparison. |
| Retire | The work is obsolete or duplicated, and data, access, billing, and integrations can be closed safely. |
| Recheck | The next review date based on renewal, risk, growth, and how quickly the product changes. |
Red flags
Slow down when any of these appear
- A critical tool is billed to a personal card or controlled by a former employee.
- Two systems can edit the same inventory, consent, fulfillment, or accounting field.
- Nobody receives or owns integration-failure alerts.
- Administrator and export access is wider than the work requires.
- The business cannot produce a usable export or explain recovery during an outage.
- Several tools are being replaced at once without mapping their dependencies.
Action plan
Turn the guide into a short piece of work
- Build the inventory from bills, app stores, credentials, and interviews.
- Trace one representative record through every critical workflow.
- Remove stale access and fix urgent ownership or recovery gaps first.
- Label each tool keep, fix, replace, or retire.
- Schedule changes around renewals and dependencies instead of doing them all at once.
- Repeat a light audit quarterly and a full audit at least yearly or after a major change.
Editorial method
How this guide was prepared
Commerce Stack Guide reviewed the official sources below and translated the decision into a small-business workflow. The guide does not claim hands-on testing and does not replace accounting, legal, privacy, security, or other professional advice where those reviews are needed.
Product prices and limits change. Use the worksheet to verify current details with representative data and a reversible test before committing.
Sources