The Orders workspace lets you review and manage orders produced through supported AIUNIFY Funnels Landing Page checkout activity.
The interface describes Orders as the area used to display and assign status to orders processed through the payment platform workflow.
Select Orders from the Ecommerce section of the authenticated navigation.
The standard Orders listing requires an authenticated user session.
The confirmed Orders controller begins its listing from Orders whose user_id matches the authenticated user.
Orders are sorted by creation date in descending order and paginated in groups of 10.
The confirmed Orders table contains these headings:
| Customer Info | Displays the customer field/value information captured during checkout. |
| Product | Displays information for the Product associated with the Order snapshot. |
| Status | Displays and allows management of the operational Order status. |
| GateWay | Displays the checkout gateway and payment state. |
| Date Info | Displays Created and Modified dates. |
| Action | Provides the available destructive Order action. |
The Customer Info column iterates through the Order's stored field_values.
Each saved key and value is displayed for review.
The exact customer fields can vary according to the checkout form used on the Landing Page.
When checkout creates an Order, the Product Name is copied into that Order.
Use the Order's Product information when reviewing the specific historical transaction instead of relying only on the Product's current configuration.
AIUNIFY Funnels supports exactly these operational Order status values through the confirmed update workflow:
| OPEN | The Order remains open for operational handling. |
| COMPLETED | The Order has been marked completed. |
| CANCELED | The Order has been marked canceled. |
The Order database structure defines:
status = OPEN
as the default for a newly created Order.
The Orders interface provides status-selection actions for:
After a valid Order-status update, the application returns:
Updated successfully
The server accepts only OPEN, COMPLETED, and CANCELED through this status-update operation.
Other values are not accepted by the confirmed controller.
The GateWay area also displays the Order's payment state.
The confirmed labels are:
| Paid | The Order's is_paid value is true. |
| Not paid | The Order's is_paid value is false. |
The Orders interface provides payment-state controls that submit either:
yes.no.The controller maps those values to the Order's boolean is_paid field.
After changing the payment state successfully, AIUNIFY Funnels returns:
Updated successfully
For supported PayPal and Stripe transactions, successful gateway completion updates the Order's payment state to Paid automatically.
Before manually changing a gateway Order's payment state, verify the transaction with the relevant merchant account when necessary.
The checkout workflow creates every new Order with Paid initially false.
COD and Bank Transfer do not contain an external gateway confirmation step in the confirmed Order-submission branch, so those Orders can remain Not paid until the business verifies payment and updates the Order appropriately.
Do not treat COMPLETED as automatically meaning Paid.
Likewise, do not treat Paid as automatically meaning the business has completed delivery or fulfillment.
These are deliberately separate fields.
The Orders interface displays the stored gateway value in uppercase.
Depending on the supported checkout method used, the stored gateway can represent values such as:
The Date Info column displays:
| Created | The date the Order record was created. |
| Modified | The date the Order record was last changed. |
Changing an Order's operational status or payment status can therefore cause its Modified date to differ from its Created date.
If the Orders workspace has no records to display, the interface shows:
No Orders found
The Action area contains the Order deletion control.
Before deletion, the interface asks:
Confirm delete?
The confirmed Order deletion workflow removes the selected Order record and returns:
Deleted successfully
The standard Order delete method does not contain a separate user-facing restoration operation.
An Order can contain important customer and payment information, so review your business record-retention requirements before deleting it.
When manually marking an Order Paid, use an independent payment source appropriate to the transaction.
For example, verify the corresponding payment in the merchant account, bank records, or COD collection process before changing the AIUNIFY Funnels payment state.
Changing an Order from Not paid to Paid updates the stored AIUNIFY Funnels payment flag. It does not itself cause Stripe, PayPal, a bank, or a customer to transfer money.
Likewise, changing an Order to COMPLETED does not submit a new gateway payment request.
Operating principle: Manage fulfillment status and payment status independently. Verify money movement before manually marking an Order Paid, and preserve required transaction records before deleting Orders.