Separate configuration from software

An unavailable product, a changed delivery fee and a revised coupon are operating decisions. They should not require customers to reinstall the app. SCALE Order reads supported catalogue, availability, fee and promotion settings from the platform. This keeps the website and app anchored to the same operational configuration.

Keep sold-out products understandable

Mark an item unavailable when it cannot be supplied. Customers can still recognise the item without being allowed to add it to a new cart. Review the customer view after the change. Existing carts and final order validation also matter: availability can change between browsing and checkout, so the final request must be checked against the current configuration.

Make fee rules explicit

Treat a service fee, a delivery fee and a delivery waiver as distinct settings. Decide whether a waiver applies to everyone or after an eligible order reaches a threshold. Review the item subtotal, discounts and fees together before publishing. Customers should understand why a fee applies, when it has been waived and how their total was calculated.

A channel change still needs a ready provider

The active registration and password-recovery channel can be configured without hard-coding it into the customer app. Only one channel is active at a time. Moving from WhatsApp to SMS is not merely changing a label: the SMS provider, credentials, delivery route and verification flow must be configured and tested first.

Know the boundary

A remote setting cannot repair native device code. Changes to Android permissions, push integrations, installed libraries or native app behaviour can require a new signed APK. Customers also need connectivity to receive current settings. Plan updates carefully and verify both the website and the installed app after a meaningful change.