Yes, two staff members may be able to add items to one table, but that alone does not tell you how a POS attributes their sales. Before buying, ask the vendor to demonstrate both actions on the same check and show the reports after it closes. The decision turns on whether the system records the person who entered each item, the check owner, or both.
Those records serve different purposes. A check owner may be responsible for closing the bill, while another server entered some of the items. If your restaurant uses sales reports to review individual contributions, you need to know which person appears in which report before you decide whether the setup is fair for your team.
Start with one table and two servers
Picture a dining room where one server starts a table and another takes over during a busy period. Both need to work with the same open check. The second server should be able to see what has already been ordered, add a late item and help close the bill without making the guest explain the whole meal again.
The owner has a separate question: what will the end-of-shift records show? A report that gives the entire check to its owner can be useful for tracking who closed it. It may be less useful for assessing each server's order entry. An item-entry record can provide another view, but it does not automatically capture every part of service, such as answering questions, running food or helping a colleague.
Agree on what you want the report to support before you see a demo. You might use it to investigate mistakes, review workload or apply a house policy for sharing tips. Ask the people affected, including servers and shift managers, what they need to see and what would make a report misleading.
Also decide who can correct an entry or transfer responsibility. A busy shift needs a workable handover, not a process that requires a manager for every routine addition. On the other hand, unrestricted changes can make it harder to understand what happened later. Ask vendors which permissions can be set for each action and what the history shows when someone makes a change.
Compare entry, visibility and attribution in a demo
Give each vendor the same requirements sheet. Toast lists a restaurant POS alongside hardware, online ordering, payments, kitchen display and integrations. Square offers a restaurant POS and related payment and order tools. Fleksa offers a restaurant POS system connected with direct ordering, reservations and related tools. Those descriptions do not answer the shared-check question; the demonstration and reporting details do.
Ask the demonstrator to use two staff identities and one open table check. Have both users open the check, then add different items close together. Watch what happens when each user saves or refreshes. Can both see the latest items? If their screens start with different versions, does the system warn them, preserve both additions or require another step?
Next, have one server take over responsibility and close the check. Ask the vendor to show the check detail, any available change history and the relevant sales reports. Do not settle for a screen showing both items on the bill. The bill proves what is on the check; it may not show who gets credit in a staff report.
Record the answer in plain language: “Item entry appears under the entering server,” for example, only if the demonstration and report actually show that result. Note the screen or report name, the setup used and any conditions. If a vendor says a different configuration changes the outcome, ask to see that configuration as well. Keep a copy of the vendor's written explanation with your requirements sheet.
Useful questions include:
- Can both servers add to the same open check without transferring ownership first?
- What does each person see after the other adds an item, and when is a refresh needed?
- Does transferring a check change earlier item attribution, later attribution, or both?
- Which report shows check ownership, item entry and closure? Can a manager retrieve the detail after the shift?
- What happens if an item is voided or corrected, and who can see the change?
For broader setup questions, Fleksa's POS questions are a starting point. Still ask for a demonstration of your own workflow; a general product description is not a substitute for seeing this check move between staff members.
Work through a late item and handover
The following is a hypothetical practice scenario, not a claim about any vendor's system. Use a demo or training environment configured so that the exercise cannot cause a real payment, guest message or courier dispatch. Do not use a real guest check or card.
Server A opens one table check and enters an $18 meal. Server B then enters a $24 meal on that same check. Both servers should verify that they can see the two items and the $42 subtotal. Server A hands responsibility for the table to Server B. After the handover, Server B adds an $8 dessert and closes the practice check. The item total is $50; this example excludes tax, tips and other charges.
Now compare the records rather than relying on the final total. If an item-entry report assigns entries to the person who made them, it would show $18 for A and $32 for B. If a check-owner report assigns the whole check to the closing owner, it could instead show $50 for B. Both views can describe the same $50 check, but they answer different questions. Confirm the vendor's actual rules rather than assuming either outcome.
Try an exception: before the handover, have A and B each add an item while both have the check open. If one addition disappears, is duplicated or cannot be attributed in the available records, ask whether the behavior can be resolved with a setting or a clear operating procedure. Repeat the exercise after any change. A workflow that depends on staff remembering to refresh may be acceptable to one restaurant and too fragile for another.
Finally, ask what happens if the dessert is entered by the wrong person and corrected. Can the manager distinguish the original entry from the correction? If not, decide whether your team can still investigate disputes with the evidence available. Do not assume that changing the displayed owner also preserves or changes the item history; ask to see the result.
Use a responsibility matrix to compare evidence
The matrix below separates the job a person performs from the record an owner needs. It uses the hypothetical check above. Replace the example outcomes with each vendor's demonstrated results when comparing your options.
| Responsibility | Person in example | Evidence to request | Decision question |
|---|---|---|---|
| Enter orders | A enters $18; B enters $24 and $8 | Item detail showing who entered each item, if available | Can you distinguish contributions on the same check? |
| Take over the check | B takes responsibility after the first two items | Owner field and any transfer history | Does a transfer alter how earlier entries appear? |
| Close the check | B closes the $50 practice check | Closed-check detail and staff sales report | Is the full total credited to B, split by entry, or reported another way? |
| Review tips | Manager reviews records for A and B | Check, staff and available tip records alongside the restaurant's policy | Do the records provide enough context for a fair review? |
Tip review is deliberately separate from sales attribution. The $50 is a sales subtotal, not a tip amount, and the example does not say how a tip would be divided. Ask whether the available records show who closed the check and what tip information a manager can review. Then compare those records with your own policy. A sales report by itself cannot establish how much work each person contributed.
Give more weight to a result you can reproduce and a written description that matches it than to a verbal promise. If a required report is missing, ask whether another available record answers the question. If the workaround is a handwritten note or manager correction, include that extra shift work in your decision. Your restaurant management software needs to support a process your staff can actually follow when the dining room is busy.
Before selection, settle on your acceptance rule. For example, if your house policy requires item-entry evidence for a shared table, a full-check total assigned only to the closing server does not meet that requirement on its own. If you only need a clear closing owner and manage shared-service reviews another way, that same report may be sufficient. Ask a qualified adviser about the legal or tax treatment of your tip policy when needed.
Next, request a demo of Fleksa's restaurant POS using the sample check. Ask the vendor to document the entry, handover, closure and reporting outcomes, including any settings needed. Compare that response with the same exercise from other vendors before choosing.
Frequently asked questions
Does the server who closes a check always get all the sales credit?
Not necessarily. A system may report the check owner, item entries or other staff details differently. Ask to see the closed check and the specific staff reports you would use.
Can two servers enter items at the same time?
That depends on the POS and its configuration. Demonstrate two staff identities working on one open check, then verify that both additions remain visible and appear correctly in the available records.
Can item sales determine how a shared tip should be divided?
Item sales show only part of the service provided. Review them alongside the check and tip records and your restaurant's policy; seek qualified advice when the policy's legal or tax treatment is in question.
