Blog · a series
The shop and the till
Selling online and over the counter from one business: one catalogue behind both, a till that is no longer allowed to choose its own total, sharing that sends a brand’s own post, and consent that belongs to the merchant.
5 parts · about 20 minutes to read them all
Part 1 · 3 min read
The shop floor and the website should not be able to disagree
Running a site on one system and a till on another means two product lists, two price changes, and a stock number that is wrong in at least one place. Web and counter are two channels of one business, so we built them that way.
Part 2 · 3 min read
The till renders a total. It does not choose one
A point of sale that trusts the total its screen sends is fine until a discount means money owed to somebody else. Our till now asks for a sale to exist, and the server says what it costs, the rule the web checkout has always followed.
Part 3 · 3 min read
Share a product, and send the brand’s own post instead of a catalogue photo
A bare product link previews as a catalogue picture and a line of copy. So when a shopper shares a product from a Rutba storefront, it shares the brand’s latest post about it (campaign photography, caption and all) with the product one tap below.
Part 4 · 3 min read
The merchant owns consent. We ship defaults that are careful about it
A Rutba storefront used to fire analytics and the Meta pixel on the first page view, in every country, with no notice. Now it asks first where the law expects it, and a shop that runs its own consent tool can take the whole decision over.
Part 5 · 8 min read
The server prices the refund, not the till
A till that adds up its own refund can pay out more than the sale took. Returns and exchanges are now priced on the server from the original sale, and at the order desk the person who collected the cash no longer confirms it.
