Change your store's rules. Promotions, shipping, returns.

Who gets which discount, what shipping costs where and what a return gets back, kept in tables your commerce team can edit. Before a change goes live, you see every basket and order it affects.

Checked
Every affected basket
Edited by
Merchandisers
Stack
Custom or headless
Runs
Cloud or on-prem
Change preview Start the 10% member discount at €60.
Rule 6 Customer tier Member · Basket value ≥ 75Basket value ≥ 60 10% off

Basket

Member customer · Fashion · €70

Discount
5% off 10% off
You pay
€66.50 €63.00

This change also touches 1 other baskets out of 36 checked.

Your store's rules are spread out. Across apps, plugins and code.

Discounts sit in a promotions tool, shipping rates in a plugin and return windows on a help page, with exceptions in a few if statements. Changing one means a ticket, and nobody can say which orders the change touches.

On a custom or headless stack, most of these rules end up in code, and every campaign waits for a developer.

Promotions
Discount codes and stacking rules in a marketing tool
Shipping
Rates per carrier in a plugin
Returns
A policy page, with exceptions handled by support
Where the rules usually live today.

One rules engine for promotions, shipping and returns.

Three tables behind every order

A store keeps its promotions, shipping and returns in three decision tables (23 rules). Change the customer, the basket or where it ships, and every answer comes back live with the rule that decided it. The bars show the same order at every basket value, so you can see where each threshold sits.

Customer
Category
Ships to
Answers
–
Round trip
–

Promotion

–

–

This order at every basket value, €10 to €400

Shipping

–

–

This order at every basket value, €10 to €400

Return

–

–

This return on every day after delivery, 0 to 90

Prices, thresholds and return windows are illustrative.

See every case that changes. Before you save.

Every case, compared

Before you save, every combination of the table's inputs is answered by the old and the new version. You see each basket and order whose answer changes, and every other answer stays as it was.

Expected answers stay put

Save the answers you rely on as tests. An edit that changes one is flagged before you save.

Live systems never break

A change that would break what a calling system sends or reads makes a new version. Systems keep the old one until you switch.

Every change on the record

The audit log keeps who changed which rule and when, next to the tests that say what it should answer.

Your systems ask over one API call, in our cloud or on your own server. API docs

Try it on your own rules.

Try it in our cloud for 14 days with no card needed, or run it on your own server. Either way, we help you move your first rules.

Also built for other teams: checkout, insurance, retail, lending and aviation.