Dedicated database hosting¶
Shared hosting is the normal starting point for a shop. A dedicated database is an optional service arranged with the ChouyLok team. Availability, hosting costs, backup requirements and a maintenance window must be agreed before a move. An Enterprise subscription does not automatically include this service.
What changes¶
All branches of one shop use one business database. A dedicated database holds that shop's products, stock, customers, sales and restaurant records separately. Your sign-in accounts, staff permissions and subscription billing stay in the platform's shared system. Your existing images and receipt links stay in use.
| Option | What it means |
|---|---|
| Shared database | Several shops use the platform's shared business storage, with shop permissions restricting access. |
| Separate database on a shared server | Your shop has its own business database, while server memory, processor and disk are still shared. |
| Separate database on a separate server | Your business database runs on another server. Hosting and network requirements need a separate agreement. |
A separate database does not reduce the number of sales you store or guarantee faster performance. Discuss your order volume, branches and recovery needs with the team. Branch and F&B subscription fees still follow your billing terms. Hosting has a separate setup fee and monthly fee, confirmed in a final quote before you pay.
Submit and track a request¶
Only the shop owner can manage this request.
- Open Settings → សេវាទិន្នន័យដាច់ដោយឡែក, immediately after Shop settings. The optional dashboard introduction appears once per shop; you can reopen the advantages from the request page.
- Choose a separate database on a shared VPS or a separate VPS package. Review the specifications and example setup/monthly prices. Example prices are provisional; the team checks capacity and approves your final quote.
- Enter your contact name and phone/email. Tap ស្នើសុំតម្លៃចុងក្រោយ (Request final quote).
- Refresh to read the approved fees and terms. Confirm them to pay the one-time setup fee plus the first month through KHQR. The team starts preparation only after bank-confirmed payment.
- View hosting invoices in this request or Billing. Hosting charges are labelled separately from your shop subscription. Use the website for payment if checkout is unavailable in your installed app.
Submitting a form does not move data or activate dedicated hosting. One open request is kept per shop. Use ដកសំណើ (Withdraw request) before payment sessions or preparation begin. Afterward, contact the team to arrange cancellation or discuss a refund. Withdrawing does not move an active shop back to shared storage.
Your first paid hosting month starts when the verified move activates your database. Later hosting invoices use the agreed monthly fee and appear before each monthly anniversary. There is no automatic bank debit. Existing dedicated shops and earlier requests keep their original agreement; they are not charged retroactively by this new request flow.
| Request status | Meaning |
|---|---|
| Submitted | The request has been received. |
| Under review | The team is reviewing the requirements. |
| Awaiting availability | The service cannot start yet. Read the team's response. |
| Awaiting payment | The team approved a final quote; confirm it and pay through KHQR. |
| Paid · awaiting preparation | Bank payment is confirmed; the team can prepare and arrange the move. |
| Declined | The request is closed. Read the response before submitting another. |
| Withdrawn | You closed the request. |
| Dedicated database activated | A verified move completed. This is historical request status. Check the current database status at the top of the page. |
The page reports an active dedicated database and warns when the shop is paused for database work. A prepared empty database alone does not mean your shop moved.
Before and after a move¶
Agree a quiet time with the team. Before the window, finish or pause selling as instructed, synchronize every POS device and report any queued or failed offline sales. Keep devices online for the final synchronization. Do not clear app data or reinstall the app to fix a pending synchronization.
During the move, shop requests pause while the team backs up, copies and verifies the business data. Wait for confirmation before resuming sales. Afterward, refresh the app and let each POS finish downloading the updated catalog. Check products, stock, branches and a recent receipt with the team. Sign-in and staff permissions continue to use the same accounts.
If the dedicated database is unavailable, the app pauses access rather than silently using an older shared copy. Contact support and wait for guidance.
Backups, restore and return to shared storage¶
Confirm backup frequency, retention and recovery expectations in your agreement. The team manages private backups and verifies a replacement database before a restore switches the shop to it. A restore returns business data to the selected snapshot: sales and changes made afterward may be absent. Discuss the snapshot, receipts and unsynchronized sales before approving recovery. Keep selling paused until the team confirms how to reconcile them.
Returning to shared storage is a separate planned move of the latest verified data. Closing a request, changing subscription plans or switching off F&B does not perform that move. To close the shop permanently, use the normal account deletion flow; contact support about pending offline data before you proceed.