Product
Connect your store — and know, at any moment, whether it is still sending
Nawras receives your orders from YouCan, Shopify, WooCommerce, a Google Sheets file, WhatsApp and your own sales page. Every delivery is verified before it is accepted, kept exactly as it arrived, then attached to the order it created. And when a source stays quiet longer than its own normal — 24 hours for a store, 12 for a carrier — Nawras is what tells you, not a customer waiting for a parcel.
Six sources, and what each one brings in
None of them is announced as “coming soon”: these are the six entries you can actually connect today.
YouCan
Every order placed on your store arrives in Nawras with the customer, their number, their city, their address and the items ordered.
You authorise Nawras from your YouCan account. Nothing to install, no address to copy over.
Shopify
Your Shopify orders come in as they are created, with the total the customer actually paid, shipping included.
One authorisation from Shopify. And if you uninstall the app, the link closes by itself.
WooCommerce
Your WordPress site sends its orders the moment they are placed, with no plugin for you to maintain.
You connect your site once; the receiving address is set by Nawras, not by you.
Google Sheets
Each row of your sheet becomes an order. Nawras re-reads the file every five minutes and only touches rows it has not handled yet.
You pick the file and the tab, then you say which column holds what.
WhatsApp
The order is built inside the conversation: the agent records the items, the city and the address as the customer writes.
You connect your number through the official API, without changing number.
Your own sales page
A homemade page or a custom checkout creates the order directly — the very same code records it as for a store.
One key generated from your account, dropped into your page.
Connecting takes an authorisation, a file, or a key
Three routes. None of them needs a developer — except the last, which is meant for those who already have one.
You authorise
YouCan, Shopify, WooCommerce
You open your store, you authorise Nawras, and that is it. The order subscription is set up by Nawras itself: there is no address to copy over, and no setting to hunt down in a menu.
You pick a file
Google Sheets
You point at the file, then you say which column holds the name, the phone, the city. And the sheet answers back: the number of the created order is written into the status column, and a rejected row carries its reason, in plain words, right there in the cell.
You drop in a key
Your sales page, your custom checkout
One key, one address, and your page records the order itself. It comes through the same door as every other source: same checks, same log, same order number.
Up to five connections per service: two Shopify stores, several spreadsheets and a WooCommerce site all fit in the same account — each with its own status, its own log and its own alert.
A connection shows what it has proven, not what you typed in
Elsewhere, an integration is “enabled” — meaning someone clicked. Here, six states, derived from what Nawras has actually observed.
Not connected
Nothing is linked. This is not a failure: it is an integration you do not use, and it reads as exactly that.
Registered
Your credentials were accepted by the service. That is all it proves — and that is precisely why this state exists: “registered” is not “verified”.
Waiting for its key
The key that lets us verify where deliveries come from is missing. While it is missing, everything is refused — nothing is accepted “in the meantime”.
Listening
The only state that amounts to proof: at least one verified delivery has been accepted. The link has genuinely worked, at least once.
Quiet
It worked, then nothing for longer than its own normal. This is the only state that depends on time passing.
Rejecting
Deliveries are arriving, and they are being refused — the stored key is not the right one. It is the only red state, and it lives alongside a setup that looks complete: that is in fact the usual case.
None of these six states is filed away in a field: they are recomputed on every view from what has been observed. A state written somewhere is a state that stays true long after it stopped being so.
A link that goes quiet comes looking for you
The threshold depends on what is speaking: what is normal for a WhatsApp number over a weekend is a breakdown for a carrier.
24 h
A store
A COD store that takes no order for a whole day is either paused or broken. Both deserve to be said out loud.
12 h
A carrier
A carrier speaks at every change of a parcel's state. Twelve hours of silence on a working day is already abnormal.
26 h
A sheet
One daily cycle, plus a delay. At exactly twenty-four hours, a slightly late run would raise an alert for nothing.
72 h
A WhatsApp number
A shop closed from Friday to Monday is nothing unusual. Seventy-two hours is the first threshold that does not shout on Tuesday morning.
You are told when the state changes, never at every check. A link broken on a Friday evening produces one notification, not sixty by Monday — that is the difference between an alert people read and alerts people end up muting.
And if the breakdown is on the service's side, it wakes us instead: when half the merchants connected to the same carrier go quiet at the same hour, your own setup is not the problem, and the alert lands with us.
Nothing is accepted without proof of origin, and nothing accepted is lost
The order of operations matters more than the list: the order is the guarantee.
Verify before writing
A delivery that cannot prove where it comes from is refused, and nothing is recorded. That is what stops a stranger from filling your log — and our bill.
Keep the delivery, look for the order afterwards
An accepted delivery is kept exactly as it arrived, before we even look for the order it belongs to. If it matches nothing, it still exists: that is what makes it possible to understand afterwards.
Know which delivery created which order
Every accepted delivery carries the number of the order it produced. That is what answers “where did this order come from?” and “what did my store actually send?” without opening another tool.
See what created nothing
Deliveries that produced no order are listed on their own, with their date and their reason. A problem you cannot see is a problem a customer tells you about.
And if writing the log itself fails, the order still goes through. A diagnostic tool has no right to cost you an order.
The questions people ask before connecting
I have no online store: I sell through ads and on WhatsApp.
That is the most common case in Morocco, and it is planned for. Your WhatsApp number is a source in its own right: the order is built inside the conversation. A Google Sheets file filled in by your team is another. And you can type an order in by hand at any time — in all three cases, same record, same tracking, same order number.
I have two stores. Do I need two Nawras accounts?
No. You can open up to five connections per service — two Shopify stores, several sheets, a WooCommerce site — inside the same account. Each keeps its own status, its own log and its own silence alert: if one goes quiet, that one is named, not “your integrations”.
My Google sheet does not have the same columns as your example.
It does not have to. You are the one who says which column holds the name, the phone, the city, the product. Nawras then writes the outcome into the status column, row by row: the number of the order it created, or the reason it was refused, in plain words. You fix the cell, you clear the status, and the row is picked up on the next run.
My sales page is homemade, with no platform behind it.
Then it is your page that creates the order. You generate a key from your account, your page uses it to send the order, and it comes through the same door as every other source. This is not a fallback path: it is the very same code that records the order, whether it comes from Shopify or from your page.
Do my carriers count as connections?
Yes, and they are watched the same way. They do not bring orders but parcel state changes — shipped, out for delivery, delivered, refused. Same six states, same log, same button to replay a delivery, with a shorter silence threshold: twelve hours, because a carrier that says nothing for a working day has a problem.
Ready to take back control?
Create your workspace in 2 minutes and see the impact in the first week.
Zero dirhams. Zero commitment. Cancel in one click.
