Managing Orders

Insites allows you to create and manage orders for the e-commerce module of your application. The following topics are discussed in detail in this document:

• Updating an order
• Managing discounts
• Managing contacts
• Managing shipping information
• Managing billing information
• Managing custom fields
• Managing notes
• Deleting an order
• Inventory
• Orders and payments
• Shopping cart

Updating an order

To update an order:

1. Navigate to Ecommerce from the main menu.
2. Select Orders.
3. Find the order you want to update and select its View row action link.
4. Select EDIT to update an order's details. You can also make changes across the following tabs:
   • Items
   • Payments
   • Contacts
   • Shipping
   • Billing
   • Custom Fields
   • Notes
5. Select SAVE.

Managing discounts

Managing contacts

Managing shipping information

Managing billing information

Managing custom fields

Managing notes

Deleting an order

To delete an order:

1. Navigate to Ecommerce from the main menu.
2. Select Orders.
3. Find the order you want to delete and click on its Delete row action link.
4. Complete the process of deleting the order using the confirmation modal.

Inventory

Take note of the following system behaviors regarding the e-commerce inventory:

• When Inventory Tracking is enabled, stocks are updated upon a successful purchase. Changes need to be applied on the application's front end for the tracking data to reflect on the UI.
• Once a product has been added to the shopping cart, product details for the purchase (i.e. prices) become the source of truth for computations in the checkout process.
• Failed transactions or refunds do not update the inventory.

Orders and payments

The following notes apply to orders and payments:

• Monetary values for Orders and Payments are stored in cents to minimize discrepancies during computations. For example, an Order amount of $1.00 is saved as 100, and $105.55 is saved as 10555.
• An Order can have 0, 1, or multiple Carts and can have 0, 1, or multiple Payments.
• Once it passes through payment, the cart should be assigned an Order UUID. This setup allows the system to display the breakdown of items purchased in Orders.
• Orders support multiple payments (e.g., installments or recurring payments). This feature must be managed on the front end, as it is suitable for a project requirement.
• Payments are associated with orders by assigning an order UUID to a payment.
• Orders and payments support partial/multiple payments. Thus, one order can have multiple payments. This feature must be managed on the front end as suited for a project requirement.

Shopping cart

The following notes apply to the shopping cart:

• There is no strict limit to the number of items stored in the cart or the duration for which items remain active in the shopping cart. The developers can set or customize these limits to align with the project's requirements.
• The cart record is deleted if an item is removed from the cart.