Going live

Checklist

Six checks run against your sandbox history and tick themselves as you go. Then you pilot one restaurant, and we watch the first week with you.

#The six checks

Check	Ticks when	How
A signed request	Any call passes the signature check with a 2xx.	Signing requests
A test store linked	Laayo Test Kitchen is linked with its code.	POST /v1/stores/link
Store status set from the POS	Open, closed or busy sent once.	PUT /v1/stores/{id}/status
An item sold out and back	An availability call goes through.	PUT /v1/stores/{id}/items/availability
A test order taken from accept to ready	One test order accepted, then marked ready.	Accept, preparing, ready
Order events received	A webhook answered 2xx, or events read with GET /v1/events.	Events

Send the test order from the Go-live page in the console. The test event button does not count for the last check; a real order event does.

Open the checklist

#Read them by API

GET /v1/partner/go-live returns the same checks, with ids signed_request, store_linked, store_status, item_availability, order_flow and events_received, and a hint for each one still open.

GET /v1/partner/go-live

200
{
  "data": {
    "ready": false,
    "passed": "5/6",
    "checks": [
      { "id": "order_flow", "label": "An order taken from accept to ready", "passed": false,
        "passed_at": null,
        "hint": "Accept, then mark ready, one test order (POST /v1/orders/{id}/accept, /ready)." }
    ]
  }
}

#Pilot one restaurant

Pick a restaurant you already work with

In Birtamod or Damak, on the Go-live page. They should be on your POS and on Laayo.

Request review

We read your request log and test orders, and reply in the console and on WhatsApp.

Get your live key

Once the review is approved. The owner then links your POS with a real code.

Watch the first week together

We follow the pilot store with you and flag anything odd before more restaurants join.

#Live for everyone

After the pilot week, your POS is listed in the Laayo vendor app as ready to connect. Any restaurant on your POS can then link in a minute.

#Before you ask

Your settings screen takes the 6 digit code and shows the linked store's name.
The secret lives on your server or in protected storage, never in a log or a support ticket.
Your POS sends a heartbeat and shows a note when the owner has taken over. See When the POS is offline.
Webhook handlers check the signature, drop repeated idempotency keys, and read the latest status instead of counting events.
Errors are shown to staff in plain words, not as raw codes. See Errors.

Nothing you do in the sandbox reaches real customers.

Was this page clear?Updated 1 Nov 2026