H&S Store

The store runs on nopCommerce, extended through its plugin model rather than modified in place. Integrations live as plugins with their own settings, scheduled tasks and admin screens, which keeps the platform upgradable and keeps each integration's failure contained to itself.

H&S already ran an ERP, and we did not touch it. We built the integration to it. Products import from it, branches and stock warehouses are modelled from it, orders are created in it and their status flows back. The website is a channel onto the business's existing inventory, not a second inventory that has to be reconciled with the first — which is the mistake that makes retail e-commerce projects fail slowly rather than quickly.

The stored-value integration carries scheduled tasks that synchronise and validate transactions independently of the checkout that created them. Payment confirmation over a third-party service is not reliably synchronous, and pretending otherwise leaves customers with money in neither place. The same pattern — settle inline where you can, reconcile on a timer where you cannot — turns up again in the TellGo build.

Card payment through MyFatoorah, the gateway GCC customers actually see at checkout, integrated as its own plugin. Store credit and reward balances settle as payment methods in their own right, so a customer with points and a card can use both.

A nopCommerce storefront carrying the full electronics catalogue, with the ERP integration keeping products, branches and warehouse stock aligned, and orders flowing back with their status.

Point-of-sale integration so the shop floor and the website are the same business, with cash, card and credit-balance tenders; reward points that customers earn and spend; and coupon and pickup mechanics for in-store collection.

MyFatoorah for cards, a stored-value integration with its own reconciliation, and reward balance as a tender — several ways to pay for one basket.

A Flutter application for iOS and Android against the same platform, now well past its fiftieth release, so the phone is a first-class channel rather than a wrapper around the website.

Every integration is a plugin with its own configuration and its own admin surface. It is more ceremony than editing the core, and it is why the commerce platform underneath stayed something that could be upgraded.

When the website and the back office disagree about stock, the back office is right, because that is where the physical goods are counted. The ERP was already there and stayed authoritative. Deciding that once, at the start, removes a category of argument that otherwise recurs forever.

Scheduled validation of stored-value transactions exists because third-party payment confirmation is not dependable in the request that started it. Building the reconciler at the same time as the integration is cheaper than building it after the first week of mismatched balances.