I need a feature the platform does not offer — what now? — answered by Engineer Saeed Baatiah
The right answer is usually a custom layer on top of the platform rather than migrating off it. Your sales, payments and shipping stay as they are, and only the missing piece is built and connected: a bespoke pricing calculator, product customisation, a reporting dashboard consolidating what the platform will not, or a wholesale order flow. That costs a fraction of a full store and solves the actual problem.
The default advice here is to stay on your platform. Salla and Zid solve local payments, e-invoicing, shipping and compliance for you — all expensive to rebuild from scratch and none of it differentiating. The useful work sits on top of the platform rather than replacing it: connecting it to your systems, automating what consumes your time, and building only the missing layer.
Practical examples of what gets built on top instead of migrating: a pricing calculator for products priced by size, quantity or specification; a wholesale order flow with different prices and limits; product customisation (engraving, colour, bespoke sizing) that carries through to the order; a dashboard consolidating figures from the store and your accounting system together; and a supplier connection that updates availability automatically.
And what gets checked first is the platform’s own limits: what its API allows reading and writing, whether it permits adding elements to the product page or the checkout step, and what constraints apply to custom apps. That is a check rather than an assumption, and its result may be that what you want is not possible on your current platform — and you are told that before you pay, not after.
- Pricing calculator, wholesale flow, product customisation, unified dashboard
- A fraction of the cost of a full store
- The platform’s limits are checked first — and the answer may be “not possible”