Write down an ordinary working day before choosing
Use a sample catalog: a simple item, a variant product, limited stock, and a product with a shipping constraint. Ask each candidate to create, edit, and export them, then complete a test order. The option that looks cheapest before staff, backups, and integrations may cost more to operate after launch.
| Solution shape | Often fits when | Resolve before choosing |
|---|---|---|
| Managed commerce platform | You want a ready operating tool and a small team | Customization limits, subscription, fees, export, and Egypt integrations |
| WordPress with a commerce plugin | You want editing in a flexible CMS your team knows | Plugin and theme updates, backups, conflicts, account ownership |
| Custom interface with commerce services | A specific experience or integration justifies custom work | Who owns catalog, orders, payments, APIs, and updates |
Score evidence instead of debating names
Give each option zero, one, or two points for catalog and variant fit, editing, the payment and shipping methods you will use, staff roles, export and restore, mobile product-page performance, and support during an outage. Weight the criteria that could stop orders. Do not score a sales promise; prove each requirement in a trial account or product documentation.
Build annual cost from subscription or hosting, processing fees, plugins, development, maintenance, backup and recovery, and the cost of moving data later. Code access does not guarantee an easy move; test exports of products, images, orders, and data formats.
Keep the decision reversible
If staff update products daily, make editing and training acceptance criteria. If a stock integration is critical, test an interruption and order reconciliation before commissioning a custom storefront. Start with the online-store readiness guide, then scope e-commerce development. Platform selection is an operating decision, so the trial should resemble real work rather than a presentation.
