Decide how many hours your team has to get an order out before it counts as overdue, at what stock level a product counts as running low, and whether another system hears about your orders. All three are on the Operations tab of Settings.
What the Operations tab holds
- In the sidebar, under Administration, open Settings.
- Select the Operations tab.
The tab holds up to four cards:
| Card | What it is for | Plans |
|---|---|---|
| Operations | Low-stock threshold and Fulfilment SLA (hours) | Every plan; the low-stock email from Growth |
| Loyalty points | The points your customers earn and spend | Growth and up |
| Search synonyms | Words that should find the same products | Every plan |
| Notifications | Order webhook URL and Webhook signing secret | Every plan |
The threshold, the SLA, loyalty points and the webhook are part of the settings form: change them, then select Save changes at the bottom of the tab. Settings saved. confirms it. Search synonyms are different: each one saves the moment you select Add.
Seeing the Operations, Loyalty points and Notifications cards needs the View settings or the Edit settings permission, and saving them needs Edit settings. Out of the box only the Store owner role has them. The Search synonyms card follows the content permissions instead, so a Store manager sees this tab with that card alone, and a role with settings permissions but without View content sees the tab without it. See Staff roles: what each one can see and do.
Fulfilment SLA (hours), and overdue orders
Fulfilment SLA (hours) is how many hours your team gives itself to get an order on its way. A new store starts at 48.
When a customer places an order, the console works out its due time: the moment it was placed plus this many hours. An order placed at 10:00 on Sunday with the SLA at 48 is due at 10:00 on Tuesday. The due time is fixed when the order is placed, so a new SLA counts for new orders only; orders already in your list keep the due time they had.
Until an order is shipped, your orders list measures it against its due time:
- Due soon — less than 24 hours left. The time since the order was placed shows in amber.
- Overdue — the due time has passed. That time shows in red.
- On time — anything else.
Hover over the time in the list to read the SLA and how long is left, or how long it has been overdue. To see only these orders, open More views above the list and choose Overdue fulfilment or Due soon. Both list orders that are Confirmed, Preparing or Ready to ship, and an overdue one of those also joins Needs attention. Once you ship an order, or it is delivered or cancelled, the clock stops.
To change the SLA, type a whole number of hours, for example 24 for next-day dispatch or 72 for made-to-order pieces, then select Save changes. If you leave the box empty or type 0, the store goes back to 48. A number with a decimal point, such as 2.5, is rounded to the nearest whole number when you save.
Read more in Why does an order need attention? and How order stages work.
Low-stock threshold, and the Low stock filter
Low-stock threshold is the stock level at which a product counts as running low. A new store starts at 5. Type a whole number and select Save changes; a decimal is rounded to the nearest whole number.
On every plan, the threshold drives your product list:
- The Stock column shows Low stock when a product’s total stock, across all its variants, is at or below the threshold but above zero. At zero it shows Out of stock.
- Select Filters above the list, then Low stock under Stock, to see only those products, so you know what to reorder. See filter your products by stock.
For example, with the threshold at 5, if Layal’s Terracotta linen dress has 2 left in size S and 2 in size M, 4 in all, it shows Low stock.
A threshold of 0 turns low stock off: nothing is ever shown as low, and no email is sent. To adjust a product’s stock, see Adjust stock and see its history.
Low-stock email alerts
Low-stock alerts are on Growth and up. Once a day, at 09:00 Amman time (06:00 UTC), we email your store’s contact email a list of every variant that is running low.
- A variant is on the list when it tracks stock and has between 1 and the threshold left. A variant at zero is out of stock, not low, and is left off.
- The subject reads Low stock alert: followed by how many variants need attention. The email lists each product with its SKU and the quantity left, and its Manage inventory button opens your product list.
- It comes in your storefront’s default language, at most once a day, and only on days when something is low.
- It goes to the Contact email on the Store tab. With no contact email, nothing is sent. See Update your store’s details.
Note that the email works variant by variant, while the product list adds up all of a product’s variants. A dress with 2 left in size S is in the email even when its other sizes are full.
On Free and Starter, a line under the threshold says Email alerts for low stock are part of the Growth plan and above. The low-stock filter in your product list works on every plan. See Plans and what each includes.
Notifications: the order webhook URL
A webhook lets another system — your accounting software, a warehouse or a spreadsheet tool — hear about your orders without anyone copying them across. Leave this card empty unless you have such a system; whoever set it up gives you the address.
- In Order webhook URL, paste the address your system gave you, for example
https://hooks.layalboutique.jo/noqta/orders. - Optionally, paste a signing secret in Webhook signing secret (see below).
- Select Save changes.
From then on, each time an order is moved to Confirmed, Shipped, Delivered or Cancelled — from the order page, from bulk actions, or through its shipments — we send that address a short message. A card order that confirms by itself once its payment goes through sends one too. A new order sends nothing until it is confirmed, and other changes, such as Preparing or Ready to ship, send nothing either.
What your developer needs to know: the message is a POST with a JSON body holding eventType (always order.status_changed), eventId, tenantId, orderId, orderNumber, fromStatus, toStatus (for example Shipped) and occurredAt (in UTC).
If the address is down or answers with an error, we send the same message again: after 1 minute, then 5 and 15 minutes, then 1, 3, 6, 12 and 24 hours, about two days in all. After the last try we give up on that message. A retry carries the same eventId as the first attempt, so the receiving system can tell a retry from a second change and should ignore an eventId it has already handled.
To stop the messages, clear Order webhook URL and select Save changes.
The signing secret, and replacing it
The signing secret proves a message really came from your store and not from someone who found the address. Make up a long random string, paste it here, and give the same string to whoever runs the receiving system.
When a secret is set, every message carries an X-Noqta-Signature header: the HMAC-SHA256 of the message body, signed with your secret and written in lowercase hex. The receiving system works out the same signature and turns away any message where the two differ.
- The box is always empty when you open the tab. We never show a stored secret again.
- Under the box, We sign every webhook with it so you can check it came from us. means no secret is set yet.
- A signing secret is set. Enter a new one to replace it. means one is stored. Leave the box empty to keep it.
To replace the secret, type the new one and select Save changes. The next message is signed with it, and so is every retry from then on, even of a message first sent under the old secret.
Warning
Change the secret in the receiving system at the same moment. Until both sides have the new one, that system turns away every message. We keep retrying each one for about two days, so messages land once the receiving system has the new secret; a message still turned away after its last retry is not sent again.
A secret cannot be removed from the console, only replaced. It can be up to 500 characters; a longer one stops the save with A webhook signing secret can be up to 500 characters.
What the form refuses
| Message | Why | What to do |
|---|---|---|
| Enter a full URL starting with http:// or https://. | Order webhook URL holds an address without its beginning, such as orders.layal-boutique.example. | Paste the whole address, starting with https://. |
| Fill in every required field. | Shown in the corner whenever a field on any of the four store tabs is outlined in red. | Find the red outline, on this tab or another, and fix it. |
| Could not save changes. | The form was fine but the save did not go through. | Try again in a moment. |
| An order webhook URL can be up to 1,000 characters. | The webhook address is longer than 1,000 characters. | Shorten it, then save again. |
| A webhook signing secret can be up to 500 characters. | The signing secret is longer than 500 characters. | Shorten it, then save again. |
| Could not reach the server. Check your connection and try again. | Your connection dropped before the save reached us. | Your edits stay on the form: save again once you are back online. |
Also on this tab: loyalty points and search synonyms
- Loyalty points — on Growth and up, the card where you turn on Run a loyalty programme on this store and set what a point earns and is worth. See Reward customers with loyalty points.
- Search synonyms — words that should find the same products in your storefront search, such as thobe and ثوب. See Add search synonyms.
On Free and Starter
Everything on the tab works on every plan except two things:
- The Loyalty points card is not shown at all.
- The low-stock email is not sent; the line under Low-stock threshold says so. The threshold still drives Low stock in your product list.
The SLA, search synonyms and the order webhook work in full. To add the email alerts and loyalty points, see Upgrade or change your plan.
What to do next
- Help customers find what you sell: Add search synonyms.
- Keep your stock right: Adjust stock and see its history.