The daily order update, and choosing its time
One message a day with the day's figures, at a time you set, and a second time if you want one. The rules on which times are allowed are the interesting part, because each of them exists to avoid telling you something untrue.
Pick one time, or two, for a daily order summary on WhatsApp. Times must be on a 15 minute boundary, at least 60 minutes apart, and inside quiet hours. The grid matches how often the sweeper runs, so an accepted time is a time you will actually be messaged at.
- One daily summary of the day's orders, sent to WhatsApp at a time you choose rather than a time we chose.
- You may set one time or two, never none and never three, and the second is for sellers who dispatch twice a day.
- Times sit on a 15 minute grid because the sweeper ticks every 15 minutes, so a time off the grid would be a promise the system cannot keep.
- Two times must be at least an hour apart, which stops a pair that would send two messages carrying almost the same figure.
- The whole schedule reuses the notification settings your other alerts already use, so there is no second place to keep it in step.
A daily summary is a small feature with a surprising number of ways to be quietly wrong. Send it at a time the system cannot honour and the seller learns the clock is decorative. Allow two times fifteen minutes apart and they pay for two messages that say the same thing. Keep the schedule in a new table of its own and it drifts out of step with every other notification setting. The rules on this page are each the answer to one of those.
What the update carries
One message, once a day, with the shape of the day: what came in, what is waiting on you, and what moved. It is a summary rather than an alert, which is why it has a schedule at all instead of firing on an event.
It goes to WhatsApp because that is where the rest of the surface already is. The same chat that can start a processing run or return a label is the one that tells you whether you need to.
It is one message by design. A stream of per order notifications is the thing sellers turn off within a week, and once it is off the useful ones are off too.
You choose the time, and you may choose two
The time is yours to set, which sounds obvious and is the whole point: a summary that arrives when you are asleep or already packing is a summary you read tomorrow, by which time it is wrong.
A second time exists for the sellers who work in two passes, a morning dispatch and an evening one. Those sellers were reading a single daily figure that was stale by the time it mattered for the second pass.
One or two, never zero and never three. Zero is better expressed by turning the update off, which is a different control and already exists. Three starts to be a stream, which is the thing the single daily message is deliberately not.
Why a time off the quarter hour is refused
The sweeper that sends these runs every fifteen minutes. So if you ask for seventeen minutes past five, the earliest it can actually go out is a quarter past, and the clock in your settings would be telling you something that was never going to happen.
Robnu refuses the off grid time rather than accepting it and rounding quietly. Rounding is the friendlier looking choice and the worse one, because it leaves you believing a fact about your own account that is not true, and you only find out by watching the clock.
This is a small instance of a rule that runs through the product: never accept a setting you cannot honour. The alternative is a configuration screen that reads like a promise and behaves like a suggestion.
Why two times must be an hour apart
Without a gap the obvious pathological pair is five o clock and a quarter past, which is two messages carrying an all but identical figure. The second one costs money and tells you nothing.
An hour is the smallest gap at which the second message is reliably about a different state of the day. It is also enough that a second dispatch pass has actually happened in between, which is the case the second time exists for.
Both times also have to sit inside quiet hours, so a schedule cannot be set to arrive in the middle of the night. A notification that wakes someone is a notification they will switch off, and then the useful ones go with it.
One message a day, at your time
A summary you read when it still matters, not a stream you mute
Where the setting lives, and why that matters
The schedule is stored on the same per seller notification settings row that already holds whether the update is on at all, alongside every other event you can be notified about.
That is a deliberate reuse rather than a new table. The tenant scoping, the on and off switch, the API and the settings screen all already existed for notifications, so the schedule inherits every one of them and there is no second preference store to keep in step.
The practical result is that the rules on this page are enforced where the value is saved, not in the screen that saves it. A time that breaks a rule is refused whether it arrives from the settings page, the API or anywhere else.
The part of this Robnu does for you
Robnu reads your Amazon account and reconciles every settlement line back to the order that caused it, so a wrong deduction is visible the day it lands.
- Orders, returns, payouts and inventory synced
- Every settlement line matched to its order
- FBA units Amazon has not made good, listed
Where this sits in the rest of your Amazon operation
On Amazon, Robnu syncs your orders, returns, payouts and inventory, reconciles every settlement line back to the order that caused it, lists the FBA units Amazon's own ledger has not made good, flags a return that never came back before the SAFE-T window closes, and scans returns in at your dock. It reads your Amazon account rather than writing to it, so accepting orders and making labels run on AJIO and Meesho today. Related reading:
Sources & further reading
- Robnu, the product the behaviour described here is the product's own. The WhatsApp surface calls the same endpoints the screens do, with the same permissions, so anything you can check on a screen is the same fact. Read 3 November 2026.
- Meta, WhatsApp Business Platform onboarding Meta's own page. It states that the 24 hour customer service window applies to messages sent through the Cloud API, and that a window opens when a person messages a business already onboarded to it. That rule is why a reply can arrive as a template rather than as free text. Read 3 November 2026.
Not legal or tax advice. Amazon changes fees, windows and policies without notice, and the detailed style guides and account-health thresholds sit behind a Seller Central login, so any figure quoted here as convention is not Amazon-published. Check anything you plan to act on against your own Seller Central account first.
Questions sellers ask
Because the sweeper that sends the update runs every fifteen minutes, so 5:07 would be delivered at 5:15 anyway. Robnu refuses the time rather than accepting it and rounding silently, because rounding leaves you believing something about your account that is not true and you would only discover it by watching the clock.
To stop a pair like 5:00 and 5:15, which sends two messages carrying almost the same figure and charges for both. An hour is the smallest gap at which the second message is reliably about a different state of the day, and it is also long enough for a second dispatch pass to have actually happened.
No, one or two. Three begins to be a stream of notifications, which is the thing a single daily summary is deliberately not, because a stream is what sellers mute within a week and muting takes the useful messages with it.
Yes, through the same on and off switch that controls every other notification event, which is a separate control from the schedule. That is why zero times is not an accepted schedule: turning it off is the right way to express that, and it already exists.
Both times have to fall inside quiet hours. A message that wakes someone is one they switch off, and when they do, every other useful notification goes with it. The quiet hours rule protects the channel rather than the individual message.
No, and that is on purpose. It lives on the same per seller notification settings row that holds every other event preference, so it inherits the same tenant scoping, API and screen. A second store for the same kind of preference is a second thing to keep in step, and it would eventually disagree.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Prepare GST Documents From A WhatsApp Chat
Ask for GST documents in the chat and Robnu prepares the month or the quarter you named. It also refuses the months a marketplace has not issued yet, and tells you the date they arrive, which is the part a spreadsheet cannot do.
Download A Shipping Label From WhatsApp In One Message
Send an order number, an AWB or a time window and the label PDF arrives in the chat, built to your own label settings. This path only re-downloads a label you already own. It never accepts an order and never mints a new one.
What A WhatsApp Chat Can And Cannot Change In Your Shop
Running a shop from a chat is only sensible if a chat cannot do something you did not intend. Here is the whole safety model: who the sender must be, which permission each action needs, and why the assistant cannot act at all.
Amazon main image rules, white background and what breaks it
The main image carries stricter rules than the rest, and breaking them gets a listing suppressed rather than flagged. What is settled, what is convention, and how to diagnose a rejection.
Amazon GTIN exemption declined and you cannot reapply
A declined exemption pins itself to your brand and no new catalogue clears it. The image rules that decide it, and the products that cannot comply.
Meesho Minimum Order & Stock: Catalog Limits and Stay-Live Rules (2026)
Meesho allows minimum 1 and maximum 9 products per catalog. Keep 20-plus units in stock to stay live and ranked. Here are the order minimums and stock rules that keep catalogs selling.
Meesho Barcoded Packaging (BP-TP): Rules & Vendors 2026
Meesho's barcoded transparent packaging (BP-TP) has been mandatory since February 2024. Here is what BP-TP means, why the QR matters, approved vendors, and what happens if you don't comply.
Meesho Branded Packaging Code: Policy & Support 2026
Meesho's branded packaging policy lets eligible sellers ship in their own brand identity within the rules. Here is what the branded packaging code covers, who qualifies, and how it sits alongside mandatory BP-TP.