Responsibility, security, evidence, payment, synchronization, reconciliation, recovery, and exit rules for Bibeno POS devices and supported offline operations.
This schedule applies only where the customer's plan and the offline POS feature gate authorize a supported device, build, branch, workflow, and offline period. It forms part of the Terms of Service and does not promise that every feature, integration, or payment method is available without connectivity.
Offline authority, cached entitlements, product data, prices, tax configuration, permissions, employee access, and transaction capacity are time-limited snapshots. A cached value may be stale. Bibeno may reduce or withdraw offline authority where the snapshot is expired, malformed, revoked, or unsafe.
The customer remains responsible for operational decisions made while current central information is unavailable, including whether to pause sales, limit value, require a manager, or use a documented fallback.
In the supported build, offline authority issued to a device is valid for at most 24 hours and must be renewed online. An offline action older than 14 days is not synchronized automatically; it is held for review instead.
A POS device may temporarily store customer, employee, catalogue, transaction, receipt, and synchronization data needed for the supported workflow. The customer must restrict physical and logical access, use screen locks and individual credentials, promptly remove former users, and report loss, theft, compromise, or unauthorized cloning.
A device must not be treated as the sole archive. Local reset, uninstall, storage failure, operating-system action, or device loss may remove data that has not synchronized.
Data loss: until the device has synchronized, its offline sales, cash movements and other offline actions exist only on that device. If the device is lost, stolen, damaged, reset by the operating system, or its storage fails before it reconnects, those actions may be permanently lost and cannot be recovered by Bibeno. The customer remains responsible for reconstructing such records from receipts, cash counts and provider statements.
In the supported build, cash is the only payment method accepted while the device is offline. Card and other external payments require a live connection and are not queued offline. Where the customer has turned on offline gift card or loyalty redemption for a device, those redemptions are limited by the signed per-device limits and checked when the device reconnects; a balance that was used elsewhere in the meantime can be overspent, and the customer carries that risk.
Bibeno does not represent that a card, wallet, bank, or other external payment is authorized merely because a sale was recorded locally. The payment provider's result and settlement records remain authoritative for external payment authorization and settlement.
Supported offline mutations carry device, tenant, branch, user, sequence, time, payload, signature, feature-gate, and idempotency evidence appropriate to the workflow. The server may reject, quarantine, or require review of an action that is expired, duplicated, malformed, unauthorized, feature-blocked, or inconsistent with current authoritative state.
The device should reconnect and synchronize as soon as reasonably possible. Queue order, dependency, idempotency, and authoritative server validation determine whether an action is accepted. A locally displayed completion state is provisional until the required server acknowledgement is recorded.
The customer must not repeatedly replay, edit, delete, or manufacture queue records to force acceptance. Recovery must use the supported queue, reconciliation, or support workflow.
Concurrent price, inventory, employee, permission, configuration, sale, refund, and payment changes may conflict. Bibeno applies the documented authoritative rule for the affected record and preserves correction or rejection evidence. A rejected mutation does not authorize an unrecorded manual financial adjustment.
For a server-confirmed held order, unchanged line items retain the product descriptions, prices, tax treatment and modifier selections recorded for that order. Where the supported build recorded a held-order recipe snapshot, those items also retain their recorded recipe and inventory quantities. Later catalogue edits do not automatically replace these recorded terms. New items and deliberately reconfigured or replacement items use the applicable current catalogue and remain subject to server validation.
A draft cart or an unacknowledged local action is not a server-confirmed historical price approval. Older orders may lack a recipe snapshot; Bibeno does not reconstruct missing historical recipes from the current catalogue. Preserving recorded product terms does not override employee permissions, order concurrency, stock controls, payment authorization, tax validation or other required financial checks.
Suspected duplicate sales or payments must be investigated using stable transaction and provider identifiers. Any correction, refund, reversal, stock adjustment, or cash adjustment must identify the original event and the authorized actor.
Offline inventory and recipe deductions are estimates until synchronized and reconciled. Consignment, supplier, purchase-order, manufacturing, recipe, modifier, and traceability actions remain subject to their current feature gates and server validation. The customer maintains physical-count, spoilage, transfer, recall, and ownership evidence.
A receipt must accurately distinguish the merchant, branch, items, taxes, discounts, payment status, tips, service charges, refunds, and any provisional or offline state that materially affects the customer. The customer must correct or reissue inaccurate evidence where the final synchronized outcome differs.
The customer reviews unsynchronized actions, quarantined or rejected records, uncertain payments, duplicate indicators, cash movements, refunds, tips, service charges, stock exceptions, and day-end totals. Review should be completed by an authorized person who did not create the exception where segregation of duties is reasonably available.
Loss, theft, unauthorized access, malware, cloning, tampering, or unexplained queue behavior must be reported promptly with the last known branch, user, device, time, and connectivity state. Bibeno may revoke the device, suspend offline authority, preserve evidence, and require re-linking or credential rotation.
Offline and synchronization evidence is retained under the applicable retention schedule and legal holds. Before device replacement, account exit, or service termination, the customer must synchronize where safe, complete reconciliation, obtain the available exports, and securely remove local data using the approved process.
Material changes to supported offline authority, evidence, risk allocation, or recovery are versioned under the legal change-control process. Support contact details are published through Bibeno's verified public facts.
Essential storage is always active. Optional analytics and marketing tools remain off unless you allow them. Read more.
