Customer content
Public banner
Business contact
Favicon / site icon
The small icon in the browser tab for the customer site and this portal. Upload a picture (a square logo works best), use a preset, or paste an image link.
Scan an order barcode (HLAB12CD) or a wig label (HLAB12CD-W1), or type it. USB scanners submit automatically when this box is focused.
Wigs cleared for release. Verify customer identity or courier reference before handing over.
| Reference | Customer | Wigs | Service | Total | Status | SLA | Payment | Source |
|---|
Clients with 2 or more active wigs — consider batch dispatch to reduce delivery cost.
Turnaround (SLA) is how long a wig on that service has from intake (when it's received) until it must be Ready for collection. A changed SLA applies to wigs received after the change.
The small icon in the browser tab for the customer site and this portal. Upload a picture (a square logo works best), use a preset, or paste an image link.
Customers enter codes at checkout; staff can apply them on walk-in bookings. A code counts as used once paid (unpaid bookings hold it for 2 hours). Dates follow Lagos time.
When an order or wig changes status and its template is set to WhatsApp, the message waits here until someone opens it in WhatsApp and presses send.
Messages open in WhatsApp on your phone or computer with the customer’s number and text filled in — you press send. Use the WhatsApp button on any order (Bookings, Wig queue, Dispatch, Scan, Accounting). Every message started is logged on the order. Status updates set to WhatsApp can't send themselves (that needs the WhatsApp Business API); they pop up for staff instead.
Templates fill in the customer’s name, booking ID, amount and tracking link. Assign a template to a status action and choose how it goes out: email sends automatically; WhatsApp pops up for the staff member who made the change (and waits under Messages) so they can send it in one tap.
For security, the Paystack secret key is not entered here. It is stored as an encrypted secret on the server (Cloudflare → Workers → this API → Settings → Variables and Secrets → PAYSTACK_SECRET_KEY). Use your sk_test_… key on staging and your sk_live_… key on production.
The Worker handles Paystack webhook events at this URL and auto-marks bookings as paid.
Add third-party scripts (live chat, analytics, pixels, etc.) that inject into the customer-facing site. Changes take effect on next deploy.
Choose a PIN between 4 and 12 characters. It is hashed and never stored in plain text.
Manage delivery cities and states. Locations are assigned to bookings and couriers for regional filtering and future multi-city expansion.
Connect Hair Laundry to external platforms like Zoho Flow or Zapier. Each webhook receives a signed POST when the specified events occur.
POST https://your-endpoint.com/hook
Content-Type: application/json
X-HL-Signature: sha256=<hmac-sha256-hex>
{
"event": "booking.created",
"data": { ...booking object... },
"ts": 1700000000000
}
| Name | Role | Last login |
|---|