Set a retention schedule by listing the reports your restaurant creates, deciding what each one is used for, and assigning an owner and a review or deletion date. Then have qualified counsel check the legal requirements before you put the schedule into practice. A useful schedule covers copies and exports, not just the report inside your ordering system.
Start with the reports you actually use. A daily order summary may help reconcile sales, while a detailed export containing guest information may need tighter access. The right period depends on the report's contents and purpose; there is no single operating rule that fits every restaurant.
Inventory reports and where copies live
Ask the people who handle orders, bookkeeping, marketing, and technology to list the reports they receive or create. Include scheduled emails, spreadsheet downloads, printed reports, shared drives, and any files sent to outside advisers. The person who runs a report may not know that someone else saves a copy each week.
For each report, record its name, source, contents, storage location, and business owner. Note whether it contains order-level details or only totals. Guest names, contact details, delivery addresses, and notes can make a detailed export more sensitive than a summary, even when both describe the same sales.
Then follow the report through its normal path. For example, an order export might begin in an ordering dashboard, be downloaded to a manager's laptop, and later be attached to an email for bookkeeping. Those are three locations to account for. Deleting the original report does not necessarily remove the other copies.
Ask the ordering provider or your administrator which reports can be exported, who can access them, and what controls are available for stored reports. Your bookkeeper can explain which records support reconciliation. A manager can identify the reports needed for staffing and service reviews. Counsel can advise on applicable legal requirements; the owner still needs to decide who will carry out the resulting schedule.
If you are reviewing the ordering setup itself, the online ordering buying guide can help frame the wider software decision. Keep this inventory focused on your restaurant's handling of reports, rather than assuming a vendor's contract-exit policy covers your own files.
Separate operating needs from legal requirements
Write down the reason for keeping each report before choosing a period. Common operating purposes include reconciling deposits against order records, investigating a guest complaint, reviewing menu performance, and comparing order volume across seasons. Different purposes can call for different levels of detail.
For instance, a manager may need individual order details to investigate a recent complaint but only monthly totals to compare seasonal sales. Keeping an aggregate report longer may meet the second need without giving more people access to detailed guest records. Check whether the summary contains enough information for its intended use before discarding the detail.
Legal, accounting, contractual, and dispute-related requirements may differ from an operating preference. Do not treat an example period or a software default as a legal retention rule. Ask qualified counsel and, where relevant, your accounting adviser which records must be kept, for how long, and whether a dispute, investigation, or other hold changes the normal deletion plan.
Also define the event that starts the clock. Does the period run from the order date, the end of the reporting month, or another agreed date? A schedule that says only “keep for a year” leaves room for inconsistent handling. Record the start event and the action at the end: delete, review, or retain under an approved hold.
Consider what you lose as well as what you keep. Shorter retention can reduce the amount of old detail staff must protect, but it may leave a gap when someone needs to investigate an older transaction. Longer retention can support comparisons and investigations, but creates more copies to secure and eventually remove. Your decision should state which need wins and why.
Build a worksheet and assign ownership
The following worksheet is a hypothetical starting point, not a recommended legal schedule. Its periods are assumptions for one restaurant's operating needs and remain subject to adviser review. The report owner proposes the period; the restaurant owner approves the operating policy after receiving appropriate advice.
| Report and location | Purpose and access | Assumed schedule | Owner and action |
|---|---|---|---|
| Daily order-detail export in a restricted shared folder | Investigate recent order issues; manager and bookkeeper access | Review six months after the report date | Manager checks for a hold, then deletes or records an approved extension |
| Monthly sales summary in the bookkeeping folder | Reconciliation and seasonal comparison; owner and bookkeeper access | Review two years after month-end | Owner confirms ongoing need and adviser guidance before deletion or extension |
| Weekly marketing export on a staff laptop | Prepare a current campaign; designated marketing staff access | Review one month after export | Marketing lead removes the local copy if no longer needed and no hold applies |
The table shows three different decisions, not three universal retention periods. In the first row, the restaurant assumes six months of order detail is useful for recent issues. It chooses a review rather than automatic deletion because an active hold or another approved need may change the action. In the second, a longer-lived summary serves comparison and reconciliation without necessarily keeping every order detail in the same folder.
For the marketing export, the practical question is whether staff need a local file after the campaign is prepared. If they do, the lead records why and sets a new review date. If they do not, the lead removes it under the approved policy. The worksheet should also list any email attachments or shared copies of that export; one row can point to a separate location list if needed.
Add a decision log with the approval date, the person responsible, the next review date, and any hold or exception. Keep the log itself free of unnecessary guest details. Set a reminder that reaches the owner of the action, not just a general inbox. If that person leaves, assign a replacement.
Agree on a hold process before deletion begins. Staff should know whom to notify when a dispute or investigation may affect a report, who can approve the hold, which copies it covers, and who can lift it. Ask counsel how the process should work for your circumstances. A manager should not decide alone that a report under a hold is safe to delete.
Test access, review, and deletion controls
Turn the worksheet into a small control check. First, pick one report in each location and confirm that its named owner can find it. Ask whether every person with access still needs it. Remove unnecessary access through the appropriate administrator, and record shared accounts or devices that make individual responsibility unclear.
Next, check how the review date will be tracked. Can the system schedule deletion, or must someone review a folder manually? If a report is emailed automatically, can the recipients or schedule be changed? If an export is copied to another device, who is responsible for that copy? Ask these as vendor and internal administrator questions rather than assuming every system handles them the same way.
Run a simulated review using a sample file with fictional data. Have the assigned owner find its location, check the pretend review date, and decide what would happen with and without a simulated hold. Document the decision without deleting live records. The exercise should not initiate a real payment, guest message, or courier dispatch. It checks whether people understand the process; it does not prove that a live deletion or every backup has been handled.
Separately, agree on a controlled live procedure for eligible records after the policy is approved. Confirm which copies are covered, whether recovery is possible, and how the action will be recorded. Ask your provider and IT administrator how backups are handled and whether deletion from a working folder also affects backup copies. Do not promise a deletion outcome until the people responsible can explain the process.
Review the inventory when a report, staff role, storage location, or ordering workflow changes. A new restaurant website or a revised export routine can create a new copy path. Likewise, a direct-order comparison may require a summary you did not previously retain. Add the report and its owner before the next scheduled review.
Next step: Choose one order-detail report and trace every copy from creation to review. Use the worksheet to assign an owner and draft a period, then ask your advisers to check it. If you are evaluating Fleksa restaurant online ordering, ask Fleksa about current US availability and the report access and export controls relevant to your setup.
Frequently asked questions
How long should a restaurant keep online order reports?
There is no single period for every report. Set a proposed period based on its purpose and contents, then ask qualified advisers about applicable requirements and any holds before approving it.
Can a restaurant keep summaries and delete detailed reports?
That may be practical when totals meet the ongoing business need, but first confirm that detailed records are not needed for reconciliation, a dispute, or an applicable retention requirement. Check all copies before carrying out an approved deletion.
Who should manage the retention schedule?
Assign a business owner to each report and a person responsible for the review or deletion action. The restaurant owner should ensure the policy is approved, advisers are consulted, and holds and exceptions have a clear decision-maker.
