N U T E K H

Systems

Heba

Built for busy kitchens

Front-of-house through kitchen payouts—menus, tickets, WhatsApp confirmations, and night-close flows calibrated for peaks and patchy uplinks.

Heba is Nutekh’s hospitality operations layer: orders, kitchen execution, stock depletion, and payouts stay connected so your margin story is visible nightly—not only when the accountant finishes Excel. It is built for venues where service speed, recipe integrity, and cash discipline matter more than generic retail POS features.

Restaurant dining room and service
Venue fit

Where Heba shines

Quick service & coffee

High ticket volume, modifiers, and hold/fire patterns. Heba emphasises tap speed, fewer mis-taps, and clear void/comp reasons for audit.

Full-service dining

Table plans, coursing, split bills, service charges, and gratuity distribution rules—without wait staff juggling three apps.

Multi-branch & cloud kitchens

Central menu pushes with local overrides, brand-level reporting, and delivery-channel tagging so margin by channel is visible.

Product depth

Modules & floor discipline

Capabilities are configured to your service model—below is the depth Nutekh typically implements.

Front of house — POS & service

  • Order modes: dine-in, takeaway, delivery, tabs, and quick-sale where needed.
  • Modifiers & holds: nested options, priced add-ons, allergy flags, and kitchen notes that actually print in the right language.
  • Table management: merge/split, transfer, and course firing aligned to your SOP.
  • Discount policies: role-gated comps, manager PINs, and reason codes for audit.

Kitchen — KDS & production

  • Kitchen display routing by station (grill, cold, bar) with bump/recall and overdue visibility.
  • Prep lists & par levels where your operation uses them—especially for high-SKU venues.
  • Recipe cards linked to stock depletion so theoretical usage tracks reality.

Menu & pricing

  • Time-based pricing (happy hour), channel-specific menus, and limited-time offers with start/stop controls.
  • Multi-language labels for kitchen chits when teams are mixed.
  • Product bundling and meal deals with clear margin guardrails.

Stock & purchasing

  • Recipe-driven depletion with wastage buckets and batch prep tracking.
  • Supplier catalogues, receiving, and variance notes on delivery.
  • Stock takes with blind counts and approval steps for high-variance lines.

People & shifts

  • Shift templates, clock-in rules, and role permissions (cashier vs supervisor vs kitchen).
  • Tip pooling options where policy allows—implementation follows your HR guidance.

Payments & close

  • Tenders: cash, card terminals, mobile money, voucher, and split payments.
  • Reconciliation helpers: expected vs deposited, shift reports, and exception queues.
  • Night-close checklist with sign-off roles so leadership trusts the Z-report.
Delivery & demand

Handoff to riders & marketing

Delivery is not “just another order type.” Heba tags channel source so you can compare net margin after fees—and when paired with Nutekh Marketing Engine, creative and paid campaigns can be measured against real basket data, not vanity clicks.

Aggregator & rider workflows

Order IDs, cancellation reasons, and re-fire discipline—so the kitchen is not guessing which ticket is still valid when networks drop.

WhatsApp confirmations

Templates and timing rules that match your brand voice—without staff copying phone numbers by hand from a notebook.

Rollout

How Nutekh implements Heba

Restaurant rollouts fail when training is theoretical. Nutekh runs service simulations before go-live.

Step 1

Menu engineering

SKU rationalisation, modifier trees, and pricing rules imported with test orders.

Step 2

Hardware & network

Printer routing, terminal placement, backup internet path, and cash-handling SOPs.

Step 3

Floor rehearsal

Peak-hour simulation, void drill, refund drill, rider handoff drill—timed and debriefed.

Step 4

Go-live hypercare

On-site/Near-site support slots, nightly metrics review for the first trading week.

Finance linkage

Heba + ImaliCloud

When you run ImaliCloud, sales, tender breakdowns, and inventory valuation can follow a controlled integration path—so AR, revenue recognition, and COGS stay aligned with what actually happened on the floor.

  • Controlled master data ownership (items, recipes, tax tags).
  • Cutover plan for opening stock and trial balance alignment.
  • Exception handling for returns, comps, and voids so month-end does not become forensic.
FAQ

Common questions

Does Heba work when the internet drops?

Nutekh designs offline/online rules per site—what can still be sold, what must pause, and how sync conflicts resolve. Details are captured in your runbook, not left to chance.

Can we keep our existing payment provider?

Often yes, subject to device/API availability. We document reconciliation between provider reports and Heba shifts.

How long is a typical implementation?

Simple QSR: a few weeks. Multi-branch with delivery integrations: longer. Your statement of work lists milestones—not generic promises.

Talk hospitality with Nutekh

Share menu size, branch count, and top three operational leaks—we will map Heba modules to match.

Talk hospitality
Related

Pair with Launch or Grow

Many venues combine Heba with Launch for brand presence, or Grow when demand and automation need to scale together.

Launch package All systems