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

POS Settings

POS Settings controls how the register behaves - what the cashier can do, what the receipt says, and which fields are captured at the counter. It has two parts: a general settings form and a data fields section.

Menu path: POS > Settings

Screenshot from the live OSOSS Dashboard

How the page is built

The general form is assembled from the settings your account actually has, grouped into sections rather than one long list. That means the exact fields you see depend on your plan and the add-ons you have activated - a business without delivery does not see delivery settings.

The Data Fields section is the second half. It controls which customer and order fields appear at the register and whether each is required. This is the same custom-fields mechanism used elsewhere in OSOSS, narrowed to the POS screen - see Custom Fields.

The decisions that matter

Whatever the exact field list, the settings on this page answer four operational questions:

QuestionWhy it matters at the counter
What can a cashier change?Discounts, price edits and voids are where cash goes missing. Permit what your supervision can review.
What does the receipt show?The customer's only record of the sale, and your first line of defence in a return dispute
What must be captured per sale?A mobile number turns a walk-in into a marketable customer; a required field the cashier cannot answer stops the queue
How does the register behave between sales?Session handling, printing and drawer behaviour

Configure the register

  1. Work through the general form section by section, and change only what you have a reason to change. Defaults on a POS are usually the safe choice.
  2. Decide the cashier's discretion deliberately: which discounts, whether prices can be edited, whether lines can be voided after being added.
  3. Set the data fields. Ask for the minimum at the counter - every required field is a few seconds on every sale, multiplied by every sale you make.
  4. Print a receipt and read it as a customer would. It should say who you are, what they bought, what they paid, and how to reach you.
  5. Have one cashier run a full test sale, a refund and a session close before you roll a change out to every branch.
Warning: Settings here apply to how the register works everywhere it is used. Test on one till before a busy day, not during one - a POS change that surprises a cashier at the counter costs the queue, not just the cashier.
Tip: Capture the mobile number, and only the mobile number, at the counter. It is the one field that turns anonymous cash sales into a customer list you can actually use later, and it takes five seconds to ask for.

Related pages