Amazon-activity push notifications
Push for Amazon activity is the headline reason most sellers want a mobile app — and it’s the deepest thing on the roadmap. Backend delivery is being built channel-by-channel; this page documents the full plan and what’s available today.
What this will let you do
A real-time pipe from your Amazon account into your phone. The four channels:
1. Order received
A push for every new Amazon order. Configurable:
- Per-marketplace toggle — pushes only for the marketplaces you actually want.
- Threshold — only push for orders over $X (skip the noise from tiny orders).
- Quiet hours — no pushes between, say, 10pm and 8am.
- Bundle — every 5 orders combined into one summary, instead of one push per order.
2. Listing change
A push when an Amazon-side change to one of your listings is detected:
- Title changed.
- Image changed (or hero image swapped).
- Price changed.
- Bullet points changed.
- Category recategorized.
- Listing suspended.
This is the second-most-requested mobile feature. Every seller has had a competitor / hijacker / contributor edit their listing without permission; catching it within minutes vs. days is huge.
3. Listing-hijack alert ⚠️
The “wakes you up at 2am” channel:
- An unauthorized seller starts selling against your ASIN.
- Your buy-box is stolen.
- A negative review wave starts (sudden cluster of low ratings).
- A counterfeit listing using your brand appears.
You configure the threshold (some sellers want every event; some want only severe ones). Defaults err on the side of fewer-and-louder.
4. Low stock
A push when an SKU drops below its reorder point:
- Configurable per-SKU threshold (defaults to your web-side reorder rule).
- Bundles into one daily summary if more than 3 SKUs cross threshold simultaneously.
- Includes a “Reorder now” deep link straight into the PO builder on the web.
How it’ll work (preview)
The pipeline:
- Amazon SP-API event arrives at Hilal’s backend.
- Hilal’s event router classifies it (order? listing change? hijack signal? low stock?).
- Channel rules decide whether to push, based on your subscription tier, your toggles, and quiet-hours.
- Expo Push delivers to your registered devices (FCM on Android, APNs on iOS).
- Tap the push → deep links into the relevant screen in the app.
Phone behavior:
- Banner with the event title (e.g., “New order: $87 — UK”).
- Sound configurable (some channels are critical and override Do Not Disturb if you opt in).
- Action buttons on the banner where appropriate (“View order”, “Mark as seen”, “Snooze”).
Mock examples
Order received:
🛒 New order: $87.40 (UK) — 1× WIDGET-A Tap to open in inbox.
Listing change:
✏️ Listing changed: WIDGET-A Hero image was replaced. Tap to review.
Listing-hijack alert:
⚠️ Buy-box lost: WIDGET-A (US) A new seller is now winning the buy box at $14.99.
Low stock:
📦 Low stock alert: 3 SKUs below reorder point Tap to review and raise PO.
Status
- Push token registration: ✅ already in place (you’ve already granted permission if you completed onboarding).
- Order-received pipe: in development; first to ship.
- Listing-change detector: in development; depends on backend listing-change-detection service.
- Hijack-detection signals: depends on Hilal’s signal-fusion module on the backend.
- Low-stock channel: the easiest of the four; depends only on the existing reorder-rule engine.
We’ll ship channel-by-channel. Order-received is the first; expect it in the next release.
Why this isn’t all live today
Push delivery for these specific events requires backend infrastructure beyond the basic Expo Push integration. Hilal’s web product already has the detection pipelines; the missing piece is the bridge that turns “detected on the backend” into “deliver to specific devices that subscribe to this user’s channels.” That bridge is being built.