Loading…

Welcome back

Here's a live view of your receipt delivery.

Today

Receipts sent
-
today
Success rate
-
delivery rate today
Shoppers reached
-
unique today
API status
Checking…
-

Last 30 days

Receipts delivered
-
last 30 days
Paper receipts avoided
-
est. replaced digitally
Cost saved
-
est. ~$0.04/receipt
Active shoppers
-
unique last 30 days
Recent receipts
DateStoreExternal IDTotalStatus
Loading…

Receipts

Find any receipt by shopper identifier, date, store, or status.

DateStoreCustomerItemsTotalStatusExternal ID
Loading…

Stores

Your registered store locations. To add or modify stores, contact contact@tabsyapp.com.

Loading…

Analytics

All metrics sourced from real receipt and delivery data. No match rates or open rates.

Receipts

This month
-
receipts sent
Last month
-
receipts sent
Delivered
-
this month
Failed
-
this month
Receipts over time
Last 6 months
By store
This month

Loading…

Status breakdown
This month
StatusCountShare
Loading…

Customers

Active shoppers
-
last 30 days
Returning shoppers
-
2+ visits in 30 days
Avg receipts/shopper
-
last 30 days
Total shoppers
-
all time (linked accounts)

Eco impact

estimates
Paper avoided (all time)
-
receipts digitised
CO₂ saved
-
kg est. @2g/receipt
Cost saved
-
USD est. @$0.04/receipt
This month avoided
-
paper receipts
Top purchased items
From last 200 receipts with item data
ItemUnits soldReceipts
Loading…

Store Profile

Shoppers see this information on their digital receipts and store page. Changes are live immediately.

Store logo
Displayed on receipts and in the shopper's store view
Logo preview
Upload a file or paste a URL. Recommended: 200×200 px, square, transparent background.
Auto-filled after upload. Or paste a public URL directly.
Public information
Shown to shoppers on receipts and the store page
The name shoppers see on all receipts.
Shoppers can contact you at this address.
Default policy values
Applied automatically to newly ingested receipts when your POS does not include warranty or return data. Leave blank to show "Unknown" to shoppers for receipts without explicit policy data.
e.g. 30 - leave blank if you have no store-wide default.
e.g. 12 - leave blank if your products have no standard warranty.
Warranty rules by product
Set warranty length by product category or by a keyword in the item name. Each item uses the first matching rule (category rules are checked before name rules); items with no match use the default warranty above. Returns always use the store-wide default. Category matching works on Lightspeed; name keywords work on all POS.

Post-Purchase Messages

Configure helpful messages shown to shoppers after their purchase. They appear inside the Tabsy shopper app, on the Stores page (on your store's card and details) - no emails, push, or SMS are sent. A message stops showing once its return or warranty window has passed.

↩  Return Reminder
Shown to shoppers before their return window closes.
Fallback used when your POS doesn't send return window data.
Shoppers will see: "Your return window closes in X days."
Warranty Reminder
Shown to shoppers before their product warranty expires.
Fallback used when your POS doesn't send warranty data.
Shoppers will see: "Your product warranty expires in X days."
Setup & Care Tips
Useful guidance shown shortly after purchase.
Accessory Suggestion
Suggest compatible accessories a few days after purchase.
Support Message
A static support contact message shown for a period after purchase.

Settings

Your account
Contact contact@tabsyapp.com to change it.
Team access

Need another person on this account? Email contact@tabsyapp.com and we'll add them with the right role.

Language

Choose the language for the retailer portal.

Change password
Letter + number + special character required.
Two-factor authentication

Checking…

Store information
Your registered details - managed by Tabsy

To update store details, branches, or API access contact contact@tabsyapp.com.

Integration & API status
Read-only diagnostic view - API key management is handled by Tabsy
API calls this month
-
total log entries
Last successful call
-
Last error
-
Connection status
-
Endpoint: POST …/functions/v1/pos-receipt
Auth: API key in X-API-Key header - issued by Tabsy admin
Docs: See your integration guide or contact contact@tabsyapp.com
Help & feedback

Need a hand, hit a bug, or have a request? Send it to the Tabsy team - we read every message.

Prefer email? Reach us any time at contact@tabsyapp.com.

Integrations

Connect your POS system or manage API keys for custom integrations. Everything receipt-related lives here.

Need help? Step-by-step setup guide · API reference

POS Connections

Loading…

Sandbox - test before you go live

Test your integration against the real endpoint without touching a real customer. Two ways, combine as needed:

  • Test API key - generate one below (it starts with tsk_test_). Every receipt sent with it is flagged as a test, lands on the shared TEST01 sandbox shopper, sends no emails or notifications, and never appears in your live stats.
  • TEST member codes - on a connected POS, ring up a sale with TABSY:TEST01 as the customer identifier (then void it). The full pipeline runs - webhook, matching, warranty and return logic - but the receipt is flagged as a test. Where you type the code differs per system (payment note, customer field, barcode) - see the guide for your POS. The result lands in the Test receipts list below - press Refresh after firing the sale.

Where the key goes: send it in the Authorization: Bearer header (or X-Api-Key). A representative payload:

curl -X POST https://zhnyoztnyvudmqpbikrj.supabase.co/functions/v1/pos-receipt \ -H "Authorization: Bearer YOUR_TEST_KEY" \ -H "Content-Type: application/json" \ -d '{ "external_id": "test-001", "receipt_date": "2026-07-12T14:30:00Z", "branch": "Dubai Mall", "currency": "AED", "subtotal": 40.00, "tax": 2.50, "total": 42.50, "payment_method": "card", "invoice_number": "INV-1042", "identifier": { "member_code": "TEST01" }, "items": [ { "name": "Sample item", "price": 40.00, "quantity": 1, "sku": "SKU-1", "warranty_months": 12 } ], "return_window_days": 14 }'

Only external_id, total and an identifier are required - everything else enriches the receipt. Leave store out and your Tabsy business name is used; put the outlet in branch. Full payload schema →

Going live: swap tsk_test_... for a live key. Nothing else changes - same endpoint, same payload. Results appear in the Test receipts list below; click a row to see the receipt exactly as a shopper would.

Custom POS - API Keys

For bespoke POS systems not listed above. Your system calls the Tabsy API directly using one of these keys. Keep keys secret - treat them like passwords.

Your API keys
Name Key Created Last used Status
Loading…
Test receipts
All sandbox traffic lands here - test keys, TEST member codes, and the "Send sample receipt" button. Never counted as errors or in your delivery stats.
WhenResultDetail
Loading…