OSOSS Help Center
العربيةOpen Dashboard

Order Rules

Order rules are the promotion engine that reads a whole order and decides what the customer earns from it: a free item, a discount, free delivery through a particular payment method, or a tiered reduction that grows with the basket. You describe the situation once, as conditions, and describe the reward once, as actions, and every order that matches is treated the same way without anyone remembering to apply anything.

Menu path: Settings > Order Rules

URL: https://my.ososs.com/dashboard/general-settings/order-rules

Screenshot from the live OSOSS Dashboard

How a rule is built

Each rule has three sections. General details carries the name, the switch that enables it, the start and end dates and the priority. Conditions is the "if" - an all/any group of tests against the order. Then is the reward. Both sides are builders: you add a line, choose a field, choose an operator, choose values.

The conditions available at order level are the facts OSOSS knows when the order is complete: payment method, order total, number of items, the customer's order and product history, order status, payment status, products, categories, customer group, delivery zone, branch, and channel - POS, online store or mobile app. That last one is how a rule is limited to a single sales channel.

ActionWhat the customer gets
Free payment methodThe fee on the chosen payment method is waived
Free order countA number of orders free
Buy X get cheapest freeThe cheapest line is free once the quantity threshold is met
Discounted orderA discount on the order, fixed or percentage
ProductsNamed products granted, with a quantity
CategoriesProducts from named categories granted, with a quantity
Tiered discountBands where a bigger order earns a bigger reduction

Every action also carries a redeem count, which caps how often that reward can be taken.

Create a rule

  1. Click the create button. The rule opens in a drawer over the list.
  2. Name it after the offer as your team says it out loud, set Start at, and leave End at empty only for a permanent rule. An end date must be after the start date.
  3. Set Priority. When several rules match one order, priority decides which is applied first.
  4. Build the conditions. Choose all when every line must be true, any when one is enough.
  5. Add at least one action - a rule with no action will not save - and set its redeem count.
  6. Save. The rule takes effect from its start date on orders created afterwards; orders already placed are untouched.

Reading the list and reusing rules

The list shows the name, start and end dates, who last changed it and a status chip: Active or Not active. A rule is only live when the switch is on and today falls inside its dates, so an expired campaign does not need deleting. Each row offers view, edit, duplicate and delete, subject to your permissions - duplicate is the fastest way to build next month's variant of a working offer, since you keep the conditions and only change the dates and the reward.

This page is the order-level half of the same engine. Its cart-level twin runs while the customer is still shopping - see Cart Rules - and both are controlled by the same permission, so a role without it sees neither page.

Tip: Turn a rule off rather than deleting it. Off keeps the definition and the history of what it did; deleted leaves you rebuilding the conditions from memory next season.
Warning: A rule that grants a discount changes what is owed on the order and therefore what posts to accounting. Test a new rule on one small order before you leave it running across every channel.

Full reference

Every option and control on this page, at a glance.

Filters (6)

Standard list tools

Every list page in OSOSS shares these controls:

Related pages

What you can do on this page

Every action on this page, step by step. What you see depends on your role, so a control your account is not set up for simply does not appear.

Delete a record

  1. Open the row's actions menu and choose Delete.
  2. Confirm in the dialog. There is no undo from the interface.
  3. If the record is referenced elsewhere - used on a document, tied to a transaction - the delete is refused and the reason shown.
When a record is refused, or when it may come back into use later, deactivate it instead of deleting. It disappears from selection lists while every document that already used it keeps reading correctly.

Export the list

  1. Filter and choose your columns first - the export mirrors exactly what is on screen, not the whole table.
  2. Click Export All.
  3. The file downloads as a spreadsheet: one row per record, your visible columns in your order.