Staff guide

The staff sign-in page inside the Blink Till app. Type your phone, then the 6-digit code from your manager or from Telegram. You stay inside the installed app the whole time.

• ·Opens by itself when the till has no session, then returns you to the screen you were going to.
• ·If you are already signed in, it takes you straight to Today.
• ·On iPhone it shows how to add Blink Till to the Home Screen from this page.
• ·Blink operators use their own sign-in page inside the cockpit, /admin/sign-in.

Requires: menu.editorders.manage(any of them)

Manage approved supplier catalogues and per-host public prices, or the host's published selection. Browsing-only venues have no counter or payment workflow here.

• ·A partner checkout accepts a voucher only within its valid dates. An old quote cannot keep an expired voucher valid.
• ·The supplier defines products and variants. Each host controls published selection, category, display order and local variant availability; supplier prices stay read-only for the host.
• ·The supplier writes one factual English/Arabic description for each collection; a missing language stays visibly unconfigured. A host may rename its public grouping but does not own supplier category facts.
• ·Archive saved products or variants to hide them while preserving host references. Catalogue drafts apply to the supplier across hosts; prices remain specific to the selected host.
• ·A request can contain up to 50 combined kitchen and host lines. Only the exact approved partnership can show its menu and history.
• ·Kitchen controls products and exact per-host prices; host chooses published products and loyalty opt-in. Host-only counter receipts use trusted menu items and quantities.
• ·Screenshot hours are informational; pauses are owned separately. Accepting a request does not credit points. Send accepted requests to the orders desk; linked payment derives eligible spend.

Start daily work from the tasks your account can do right now. Today shows up to three task groups chosen from your account permissions and what your venue has switched on: Counter (find or scan a member, start a new member), Shift (open order tickets and partner counter work, only when orders are on and you can manage them), and Venue tasks (menu availability and content gaps, partner catalogue, public menu preview). Below them, accounts that can view venue activity get a compact row of today's numbers against yesterday (loyalty numbers only when loyalty is on for the venue), then today's member activity when loyalty is on. Every other screen you can open is in the bottom bar or More. Owners also get a collapsible venue setup checklist.

• ·Orders opens on recent tickets. Start an order opens catalogue search and category filters, and the basket review appears once items are added.
• ·Task groups follow your effective permissions and venue setup, never the preset name. Groups with nothing to act on are hidden.
• ·Open tickets lead the screen when orders are waiting. If the ticket status cannot be read, Today says so instead of showing zero.
• ·Today's numbers, for accounts that can view venue activity: taps and customer page views, plus new members, earns, redeems and spend recorded for points when loyalty is on, each with yesterday beside it. The screen refreshes on its own, faster while you are using it.
• ·Owners see contact and customer-link setup on Today, in a collapsible section. Menu and loyalty checks appear only when those features are enabled for their venue; a QR-only venue does not need an NFC chip to complete the link check.

Requires: members.view

The center button (when loyalty is on for the venue) and the heart of the counter. Find a member first: type a card code, name or phone, or scan their card. The member screen shows who they are, the points balance with when it was last confirmed, and only the actions your account may take: Add points, Use reward, then vouchers, member details and the welcome check. It replaces the old Earn, Redeem, and Members screens (their routes redirect here).

• ·One search box: phone number, the 4-letter member code, or a name. Egyptian numbers work as 01XXXXXXXXX.
• ·Unknown phone becomes a new member in one tap; the name is optional.
• ·A provisional new card shows its saved welcome terms as pending. Staff with redemption access check the code shown on the customer's device and attest the in-person confirmation before activating the welcome benefit once. This does not verify a phone.
• ·Add points: enter only spend eligible under the business loyalty rules, in EGP, with a live points preview and the earn rule beside it. Review the bill yourself; manual entry does not automatically exclude products. A confirmed earn stays on screen as a receipt with the new balance; if it matches an earlier confirmed earn it says Already recorded and nothing is added twice. Optional visit points and bonus chips depend on the program.
• ·At a protected browse-only partner host, select only that venue's own eligible menu items and quantities, enter the amount actually paid after discounts, and confirm your payment attestation. The receipt records the selected items and paid amount; it is a staff statement, not payment-provider verification. Partner items cannot earn through this form.
• ·Use reward: the program's reward list; anything the balance cannot afford shows disabled with how many points are missing. Review opens the confirmation: the reward, its cost, and the balance after, then Confirm redemption.
• ·Stamp cards: when the venue's program earns per visit only, the member screen says stamps, Add stamp is one tap, and a row of dots shows how close the next gift is (a gift icon marks each reward, and what is ready to give is named). A second stamp inside the visit window is refused with when the next one is possible. Game prizes and bonus taps never block a visit stamp.
• ·Typing a full 11-digit number or a member code opens the member on its own.
• ·Vouchers (under Other actions): issue campaign vouchers and use the ones customers show; used or expired ones stay visible.
• ·Member details (under Other actions): view and update the member's name and notes. Staff can never delete a customer or any history; that stays with the operator.
• ·If an answer is unclear, the till never says it failed or worked. A redemption or voucher request reopens as Check the result: Check status re-sends the same request so it cannot count twice, and Next member keeps it waiting until you reopen that member. An earn with no clear answer waits on this phone and sends itself.
• ·When Blink views the app as a staff account, the write controls stay visible but turned off, with the reason.
• ·Double-tap and bad-network safe: repeating a confirm never double-charges. Every success celebrates with a count-up and a haptic tick.
• ·Redeem asks first: the reward, what it costs, and the balance the member is left with. Redeemed on the wrong person? Undo sits next to the reward for two minutes and puts the points straight back. Undo is its own permission: it shows only for someone allowed to reverse a redeem, and only for the person who made it.
• ·When a money action is refused, the till says why in the language it is running in, not in English.
• ·Under the actions, the member's last 20 movements, each one naming the hand behind it: who added or spent the points, when, and the bill amount on an earn. A customer asking "who gave me these?" is answered at the counter now, not by calling the owner.
• ·An earn typed while the line is down is saved on this phone and sends itself when the connection is back; the amber pill counts what is waiting. With no signal the search also falls back to the last 25 customers this till opened, and their balance is shown with the time it was last read, never as a current number. Redeem is different, it needs the network: giving away a product on a guess is worse than waiting a second.
• ·The protected native-item receipt needs a live connection and never joins the offline earn queue. If the response is lost after you confirm, check the pending receipt before trying again; a matching retry uses the original request identity.

Requires: points.redeemmenu.edit(any of them)

Only appears while the business has an event configured.

The event lifecycle console. Create an activation with the wizard, run the counter while it is live, pause and resume it, then retire it into a frozen report kept in the archive. A business can also run an evergreen registration with no live event. While an event is configured it can take the one extra bar slot, after Orders; otherwise it sits in the More grid, where managers with no event can also start one or read past reports.

• ·Create wizard: name (EN + AR), sign-up voucher percent, optional order items, optional prizes. The campaign key is generated for you.
• ·Member lookup scoped to the event: short code, phone (or its last digits), or name.
• ·Order builder: tap items to build the order; the member's active campaign voucher applies its discount automatically.
• ·Collect runs as one transaction: the order, the voucher redemption, and points on the discounted net. Safe against double-taps.
• ·Live price edits: adjust items and the discount mid-event; the next order picks them up instantly.
• ·Prize draw among registrants who have not won yet, with a running winners list. Hidden when the event has no prizes.
• ·Pause and resume without losing anything; retiring freezes a final report into the archive.

Requires: menu.edit

Edit your venue's menu yourself, no need to ask anyone. Sections, items, prices, and availability, with every change live on the customer menu the moment you save it.

• ·The menu card at the top says whose menu this is. Items here belong to the venue; a partner supplier's items keep the supplier's name and are managed under Partnerships. In the item sheet, set Name, Price, Photo and Available to guests, then tap Save to live menu. A new photo saves as soon as you pick it.
• ·Sections: create, rename (with optional Arabic name), reorder, hide or show, and delete with a two-tap confirm. Section options (hide or show, edit, reorder, delete) sit behind the options button next to the section name.
• ·Each category can have an optional factual English and Arabic description, up to 500 characters each. Missing translations stay unconfigured and save without changing item prices or photos.
• ·Items: name, Arabic name, description, and price; reorder from the item's Reorder or delete control (Move up / Move down).
• ·An unconfirmed currency is shown as a source amount, not an EGP price. Editing preserves the saved currency; confirm it before publishing.
• ·Sold out in one tap: the item stays on the menu, greyed with a sold-out tag, and comes back in one tap.
• ·Add or replace item photos. Blink compresses each image on the phone and stores it in its own database.
• ·You only ever see and edit your own venue's menu.

Requires: menu.edit

Decide what customers see first on your venue page: the order of its parts, a headline, an item of the day, and custom menus with their own days and hours. Owners and managers only. Nothing changes for customers until you tap Save.

• ·Page order: move each part up or down and hide the ones you do not need. Pay and Visit and contact always show, because your printed pay sign and your contact details land there.
• ·Item of the day: an ordered list. The first one that is on and inside its hours shows; if that item is sold out, the next one in its hours shows instead until it is back.
• ·Custom menus: a name, a short note, items picked from your menu with search, and a schedule. Only in this menu takes those items out of the main menu and shows them only there, during its hours.
• ·Custom menus can include your partners' food. Partner items show the partner's name and your price; if the partnership is paused they stay in the menu but do not show to guests.
• ·Schedules run on Cairo time: pick days (the week starts Saturday), an optional from and to time, and optional first and last days. Nothing picked means always.

Requires: orders.manage

Counter and table tickets in one iPad-friendly workspace. Choose available menu items, review quantities and the total, send the ticket, then keep its kitchen status visible without leaving the screen.

• ·Items, names and prices come from the active menu and are checked again by the server when the ticket is placed.
• ·Each ticket uses one retry key. If a connection drops after sending, Retry safely recovers the same ticket instead of creating a duplicate.
• ·Open tickets come first, newest status at a glance; completed tickets fold under Completed. The review bar appears only once you add items.
• ·The cashier sees active and recently completed tickets here while taking the next order.
• ·Queue polling is tenant-scoped. When the network is lost, the last successful list stays on screen and new submissions pause until the connection recovers.
• ·The line at the top shows when the list last updated. If the connection drops it says so and shows the last update time; check the ticket status before changing it again.
• ·When a Blink operator views the app as a staff account, this screen is view only: changes are switched off.

Requires: orders.manage

A clear four-step board for new, accepted, preparing and ready tickets. New tickets are checked every few seconds, and each action moves the ticket forward for the whole team.

• ·Each ticket shows the counter or table label, time, item quantities and saved price snapshot.
• ·Large, high-contrast status actions follow the allowed order lifecycle.
• ·The last successful queue remains visible during an outage with a stale connection indicator.
• ·The line at the top shows when the list last updated. If the connection drops it says so and shows the last update time; check the ticket status before changing it again.
• ·When a Blink operator views the app as a staff account, this screen is view only: changes are switched off.

Requires: members.view

Every member of your venue in one list, newest activity first. Until now the only way to reach a customer was to know their phone number or member code; this is the list you can actually read, sort and page through.

• ·A Find a member row at the top opens the Loyalty center search: card code, name or phone.
• ·Sort by recent, name, points or visits, and page through 25 at a time.
• ·Every row opens that member in the Loyalty center, where adding and redeeming points already live.
• ·Only this venue's members are ever listed, proved in the query itself.

Requires: activity.view

This month next to last month, for the numbers a venue actually renews on: how many members joined, how many came back, how many stopped coming, the points moving, and the EGP the till recorded. Nothing here is a promise; it is what your own counter did.

• ·This month against last month, side by side, so a change is visible without doing arithmetic.
• ·Came back and stopped coming, counted from real member activity, not from an estimate.
• ·The EGP line is the amount cashiers typed at the till. If nobody typed an amount, it reads zero and says so.
• ·On a stamp card the screen counts stamps instead of points, hides the EGP line (a stamp card records no spend) and shows gifts used; Today reads the same way.
• ·Taps by placement: which door decal, table tent or card people are actually tapping.
• ·An honest empty state: a venue with no history says so instead of showing invented numbers.

Requires: menu.edit

Your venue's public profile: contact info, hours, social links, and payment links (InstaPay and Vodafone Cash). What you save here is what customers see on your venue pages. Name, web address, and brand colors stay with the operator.

• ·Contact block: phone, WhatsApp, address, and the maps link customers tap.
• ·Opening hours drive the open-now line on your venue page.
• ·Social links: Instagram, Facebook, and friends, shown on the info page.
• ·Payment links: an InstaPay link and a Vodafone Cash number customers can copy. Blink never processes the payment itself.
• ·You can update the public profile and menu. Blink activates the loyalty program and creates staff accounts for your venue.

Requires: links.manage

The NFC cards and QR codes assigned to your venue, with their tap counts. You point each one at the right destination; registering new physical chips stays with the operator.

• ·Preview or download your assigned QR with the Blink logo on white. Scan a printed proof before reprinting cards or tents.
• ·Open an assigned piece's print preview for branded counter, table or sticker SVG, full-size PNG and PDF. It uses the existing stable target; preview never creates a link or claims a physical scan.
• ·Every active link shows its placement (table 4, counter, door) and how many taps it got.
• ·Retarget the destination live: the physical card never needs rewriting.
• ·Destinations can be your venue pages or an outside URL.

Make the counter phone comfortable: install the app to the home screen, turn on push notifications, keep the screen awake through a shift, and manage your account.

• ·Who is signed in and Sign out of this device come first, for shared counter phones. The customer wallet link opens the guest page customers use for their own cards; it is not your staff account.
• ·Install guide: add the app to the home screen so it opens full-screen like a real app.
• ·Push notifications opt-in for staff pings.
• ·Keep-screen-on toggle for long counter shifts.
• ·Account block: your name, venue, and role, plus logout. Sessions last 180 days so you are not re-typing codes mid-shift.