Carts & Orders
Orders
Orders are created at the end of the Checkout process, just before the payment is confirmed.
Blueprint
If you need to add additional fields to orders, you can do so by updating the Order blueprint, found on the "Blueprints" page in the Control Panel:
The blueprint only contains your custom fields. They'll be merged with Cargo's built-in order blueprint.
Statuses
Orders can move between various different statuses:
- Payment Pending
- Payment Received
- Shipped
- Returned
- Cancelled
You can change an order's status manually on the order details page in the Control Panel:
Sometimes, an order's status may be updated automatically. For example: an order will move to "Payment Received" when a payment has been confirmed.
Shipping
When you change an order's status to "Shipped", Cargo will let you input a "tracking number" for the order and will give you the ability to print/download a packing slip.
If you want to customise the packing slip, you may publish it with the following command:
php artisan vendor:publish --tag=cargo-packing-slip
Storage
Out of the box, orders are stored as YAML files in the content/cargo/orders directory. If you wish, you can change the directory in the cargo.php config file:
// config/statamic/cargo.php
'orders' => [
'repository' => 'file',
'directory' => base_path('orders'),
],
Database
You can also opt to store orders in a traditional database, which might be useful for high-traffic stores.
To move orders to the database, run this command:
php please statamic:cargo:database-orders
It'll automatically publish database migrations, update your cargo.php config file and import existing orders into the database.
If needed, you can customise the eloquent models Cargo uses by updating the model and/or line_items_model keys in the cargo.php config file.
As a reminder, make sure you have a backup strategy in place before switching to database orders in production, in case the worst happens.
Both Laravel Forge and Ploi have built-in solutions for database backups.