高峰期断网——POS能否继续销售而不丢数据？

断网不应迫使门店停业、重复交易、丢失支付或破坏库存。了解离线交易、本地存储、支付限额、小票编号、库存冲突、延迟同步与恢复测试。

离线模式是业务连续性能力，而不是一个勾选项

Offline mode is a full business continuity design covering products, prices, taxes, permissions, payments, receipts, storage, inventory, and later synchronization.

The system should clearly define which actions continue offline and which require central data.

考虑一个真实断网场景：Offline mode is a full business continuity design covering products, prices, taxes, permissions, payments, receipts, storage, inventory, and later synchronization. Local records should contain complete sale details, device, employee, branch, sequence, and synchronization status. Offline card payments require separate risk limits because later authorization can fail. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Idempotency is required so retrying synchronization does not create duplicate sales. Receipt, order, and transaction identifiers must remain unique across all devices. The system should clearly define which actions continue offline and which require central data. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Sensitive data should remain encrypted and role-based access should still apply without the server. Stores should deliberately test outages, restarts, reconnection, duplicates, inventory, receipts, and payment settlement. When connectivity returns, transactions should upload through a controlled queue with confirmation and retry handling. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

本地交易需要持久且加密的存储

Every offline transaction must be saved immediately to durable local storage that survives restart, logout, battery loss, or crash.

Local records should contain complete sale details, device, employee, branch, sequence, and synchronization status.

考虑一个真实断网场景：Local records should contain complete sale details, device, employee, branch, sequence, and synchronization status. Limits can depend on amount, card type, branch, device, customer risk, and outage duration. Every offline transaction must be saved immediately to durable local storage that survives restart, logout, battery loss, or crash. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Stores should deliberately test outages, restarts, reconnection, duplicates, inventory, receipts, and payment settlement. Conflicts can involve stock, prices, customers, refunds, and simultaneous online activity, and rules should be visible. Conflicts can involve stock, prices, customers, refunds, and simultaneous online activity, and rules should be visible. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

支付需要独立的离线风险规则

Sensitive data should remain encrypted and role-based access should still apply without the server.

Offline card payments require separate risk limits because later authorization can fail.

考虑一个真实断网场景：The system should clearly define which actions continue offline and which require central data. Idempotency is required so retrying synchronization does not create duplicate sales. Offline mode is a full business continuity design covering products, prices, taxes, permissions, payments, receipts, storage, inventory, and later synchronization. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Receipt, order, and transaction identifiers must remain unique across all devices. Every offline transaction must be saved immediately to durable local storage that survives restart, logout, battery loss, or crash. Limits can depend on amount, card type, branch, device, customer risk, and outage duration. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：When connectivity returns, transactions should upload through a controlled queue with confirmation and retry handling. Offline mode is a full business continuity design covering products, prices, taxes, permissions, payments, receipts, storage, inventory, and later synchronization. Idempotency is required so retrying synchronization does not create duplicate sales. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Local records should contain complete sale details, device, employee, branch, sequence, and synchronization status. Limits can depend on amount, card type, branch, device, customer risk, and outage duration. Every offline transaction must be saved immediately to durable local storage that survives restart, logout, battery loss, or crash. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Offline card payments require separate risk limits because later authorization can fail. Sensitive data should remain encrypted and role-based access should still apply without the server. Sensitive data should remain encrypted and role-based access should still apply without the server. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

小票与订单编号必须保持唯一

Limits can depend on amount, card type, branch, device, customer risk, and outage duration.

Receipt, order, and transaction identifiers must remain unique across all devices.

考虑一个真实断网场景：Sensitive data should remain encrypted and role-based access should still apply without the server. Stores should deliberately test outages, restarts, reconnection, duplicates, inventory, receipts, and payment settlement. When connectivity returns, transactions should upload through a controlled queue with confirmation and retry handling. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Offline mode is a full business continuity design covering products, prices, taxes, permissions, payments, receipts, storage, inventory, and later synchronization. Local records should contain complete sale details, device, employee, branch, sequence, and synchronization status. Offline card payments require separate risk limits because later authorization can fail. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

同步必须透明地解决冲突

Idempotency is required so retrying synchronization does not create duplicate sales.

When connectivity returns, transactions should upload through a controlled queue with confirmation and retry handling.

考虑一个真实断网场景：Every offline transaction must be saved immediately to durable local storage that survives restart, logout, battery loss, or crash. The system should clearly define which actions continue offline and which require central data. Receipt, order, and transaction identifiers must remain unique across all devices. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Limits can depend on amount, card type, branch, device, customer risk, and outage duration. When connectivity returns, transactions should upload through a controlled queue with confirmation and retry handling. Stores should deliberately test outages, restarts, reconnection, duplicates, inventory, receipts, and payment settlement. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Conflicts can involve stock, prices, customers, refunds, and simultaneous online activity, and rules should be visible. Offline card payments require separate risk limits because later authorization can fail. Local records should contain complete sale details, device, employee, branch, sequence, and synchronization status. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：Every offline transaction must be saved immediately to durable local storage that survives restart, logout, battery loss, or crash. The system should clearly define which actions continue offline and which require central data. Receipt, order, and transaction identifiers must remain unique across all devices. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

应在下一次断网前测试恢复

Conflicts can involve stock, prices, customers, refunds, and simultaneous online activity, and rules should be visible.

Stores should deliberately test outages, restarts, reconnection, duplicates, inventory, receipts, and payment settlement.

考虑一个真实断网场景：Offline card payments require separate risk limits because later authorization can fail. Sensitive data should remain encrypted and role-based access should still apply without the server. Sensitive data should remain encrypted and role-based access should still apply without the server. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。

考虑一个真实断网场景：The system should clearly define which actions continue offline and which require central data. Idempotency is required so retrying synchronization does not create duplicate sales. Offline mode is a full business continuity design covering products, prices, taxes, permissions, payments, receipts, storage, inventory, and later synchronization. 应测试现金、离线刷卡、设备重启、两台终端销售同一低库存商品、中心改价、重复同步重试以及上传前退款。