Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AndrewwCO/Admin-Pana/llms.txt

Use this file to discover all available pages before exploring further.

The Orders page gives administrators a paginated view of every order placed across the Panahashi platform. You can monitor orders through their status lifecycle, open a detail panel to see items and payment information, update an order’s status, and issue refunds when a payment has been approved. Orders are loaded 20 at a time using previous and next page controls.

​
Order table

The orders table loads data from the backend and displays it in rows. Each row shows:
  • ID — first 8 characters of the order UUID
  • Customer (userName)
  • Bakery (bakeryName)
  • Total — order total in local currency format
  • Status — color-coded order status badge
  • Payment — payment status displayed in a colored text badge
  • Date — order creation timestamp
Click the Gestionar button on any row to open the order detail modal for that order.
The orders table is paginated at 20 records per page. Use the arrow buttons at the top right of the page to navigate between pages. The Next button is disabled when fewer than 20 orders are returned, indicating you are on the last page.

​
Order status lifecycle

Orders progress through a defined sequence of statuses. An order can also be cancelled at any point before completion. 
PENDING → CONFIRMED → BAKING → READY → COMPLETED
                                      ↘ CANCELLED
StatusBadge colorMeaning
PENDINGYellowOrder has been placed but not yet acknowledged by the bakery.
CONFIRMEDBlueThe bakery has accepted the order and will begin preparing it.
BAKINGOrangeThe order is actively being prepared in the kitchen.
READYTealThe order is ready for customer pickup.
COMPLETEDGreenThe customer has collected the order.
CANCELLEDGrayThe order was cancelled before completion.

​
Payment statuses

Each order carries an independent payment status tracked alongside the order status.
Payment statusBadge colorMeaning
PENDINGYellowPayment has been initiated but not yet processed.
APPROVEDGreenPayment was successfully charged.
REJECTEDRedPayment failed or was declined.
REFUNDEDPurpleA refund was issued for this order.

​
Order detail

Click the Gestionar button on an order row to open the order detail modal. The modal shows a full summary:
  • Order ID, customer name, and bakery name
  • Pickup time and order notes (if provided by the customer)
  • Order total and discount amount
  • Payment method and payment status
  • Current order status
  • Items list — each product shows its emoji, name, quantity (qty), and line total (unit price × quantity)

​
How to change an order’s status

1

Open the order detail

Click the Gestionar button on the order row to open the detail modal.
2

Select a new status

In the Cambiar estado section of the modal, click one of the status buttons. The button for the current status is highlighted and disabled; all other statuses are selectable.
3

Confirm the change

Clicking a status button immediately sends a PATCH request with the chosen status:
{
  "status": "CONFIRMED"
}
The detail modal and the order row in the table both update to reflect the new status.

​
How to process a refund

Processing a refund is immediate and irreversible. A browser confirmation prompt appears before the request is submitted. Once issued, the payment status changes to REFUNDED and cannot be undone.
The Procesar reembolso button appears in the order detail modal only when the order’s paymentStatus is APPROVED. It is not shown for orders with other payment statuses.
1

Open the order detail

Click Gestionar on the order row. Confirm that the payment status shows APPROVED.
2

Click the refund button

Click Procesar reembolso in the Reembolso section of the modal.
3

Confirm in the browser prompt

A confirmation dialog asks you to verify. Confirm to proceed.
4

Refund is processed

The admin panel sends POST /api/v1/payments/order/:id/refund. On success, the payment status updates to REFUNDED (purple) and the refund button disappears.

Build docs developers (and LLMs) love

Get started for freeTalk to us