Saizeriya Tool Suite

The Saizeriya Order Protocol defines a compatibility layer for a table-based ordering system. It exposes the same application under /saizeriya2/ and /saizeriya3/ paths.

Core Workflow:

1. A QR URL or direct URL resolves to a table session.
2. The first access displays the entry page.
3. Navigation is form-based: the client submits a form#frm_ctrl via POST to ./?{urlId}, setting hidden fields like proc and ctrl.
4. Ajax endpoints under ./src/cmd/*.php handle status checks, item lookups, and staff calls.
5. Submitting an order moves cart lines to submittedOrders, clears the cart, and renders the call page.

Clean-Room Implementation Rules: When implementing a compatible server, you may preserve URL paths, HTTP methods, form/JSON field names, selector names (used as API hooks), page state names, and numeric limits.

You must not copy the original source code, exact UI strings, HTML structure (except required hooks), CSS, images, icons, fonts, audio, or proprietary branding. Use semantic message keys (e.g., last_order_closed, empty_cart) instead of reproducing historical wording.

The main page displays the current cart and allows for quantity adjustments or item removal.

Row Removal and Quantity

• Remove Row: Clicking .del triggers a confirmation dialog. Upon confirmation, the row is removed and totals are recalculated.
• Adjust Quantity:
  • .minus decrements the quantity (minimum 0 for .zero inputs, otherwise 1).
  • .plus increments the quantity up to 99.

Submission Flow

1. Add More: .command #menu checks last-order state. If clear, submits proc=menu.
2. Submit Order: .command #order sums quantities and checks if the cart is empty. If valid, it shows a confirmation dialog.
3. Finalize: Upon confirmation, it submits proc=order.

Server Side Processing: On POST with proc=order, the server reads the following arrays:

• item[id][]: Item IDs
• item[count][]: Quantities
• item[reorder][]: Reorder flags
• item[mod_id][]: Modifier IDs
• item[mod_count][]: Modifier quantities`

When the server returns a page, it must perform specific HTML rewrites to ensure compatibility with the protocol. This includes updating action URLs, data attributes, and specific DOM element values.

Required Rewrites:

1. Actions: Replace action="./?..." with action="./?{nextId}".
2. Data Attributes:
   • Replace data-shop="..." with the current shopId.
   • Replace data-tbl="..." with the current tableId.
3. DOM Values:
   • Set #shop-id to shopId.
   • Set #table-no to tableId.
   • Set #session-id to sessionId.
   • Set #number to peopleCount.
   • Set hidden name="token" to token.
4. Page-Specific Logic:
   • entry page: Expose current table ID and initial party-size in #number, keep cart empty, and render as a start-order page.
   • history / account pages: Replace submitted-order rows and totals.
   • receipt page: Replace table ID and checkout code.

The following table defines the expected flow of operations, the AJAX calls triggered, the submitted form fields, and the resulting page for each step in the ordering process.

Note on Last-Order State: When the last-order state is closed, order-entry paths must submit proc=account and ctrl=clear.