Connect your Loaded Commerce store to EcomCentral using Bearer token authentication with your API key from the admin panel.
Loaded Commerce (loadedcommerce.com) is a US-based open-source e-commerce platform
derived from osCommerce and Zen Cart, widely used by small and mid-sized US
retailers. The modern version — Loaded7 — adds a REST API module and a
contemporary admin interface while retaining the osCommerce field-naming conventions
(products_model, orders_id, customers_name, etc.).
{store_url}/api/v1. The REST API module must be enabled in the admin panel
before credentials will work.
/api/v1/https://your-store.com/api/v1/products?limit=1
— you should see a JSON response (or a 401 Unauthorized, which confirms the endpoint exists)https://mystore.com| Key | Required | Description | Example |
|---|---|---|---|
store_url |
Required | Full root URL of your Loaded Commerce store. EcomCentral appends /api/v1 automatically. Do not include a trailing slash. |
https://mystore.com |
api_key |
Required | API key from the Loaded Commerce admin API settings. Sent as Authorization: Bearer {api_key} on every request. |
abc123xyz... |
url for the store URL;
apiKey or token for the API key.
| Operation | Method | Endpoint |
|---|---|---|
| Test connection | GET | /products?page=1&limit=1 |
| List orders | GET | /orders?page=P&limit=N |
| Order detail | GET | /orders/{id} |
| Add tracking | PUT | /orders/{id} with { "tracking_number":"…", "orders_status":"Shipped", "comments":"…" } |
| List products | GET | /products?page=P&limit=N |
| Product detail | GET | /products/{id} |
| Update stock | PUT | /products/{id} with { "products_quantity": N } |
Authorization: Bearer {api_key}. List endpoints
return a plain JSON array. The total count is read from the X-Total-Count response
header when available, falling back to the array length. Single-item endpoints return the object
directly without an envelope wrapper. Field names follow the osCommerce convention
(products_model, orders_id, customers_name, etc.).
Loaded Commerce uses text-based order statuses (inherited from osCommerce). EcomCentral recognises the following and displays them with colour-coded badges.
| Status | Badge colour | Notes |
|---|---|---|
| Delivered / Completed / Shipped | Green | Also: Complete, Closed |
| Pending / Processing | Blue | Also: Payment Received, New, Awaiting Fulfillment |
| On Hold | Amber | Also: Awaiting Credit, Partially Shipped, Backordered |
| Cancelled / Refunded | Red | Also: Canceled, Denied, Failed |
| Any other value | Blue (default) | Unknown statuses default to blue |
| Feature | Supported | Notes |
|---|---|---|
| View orders (paginated) | ✅ | Order ID, reference number, date, status, total + currency code |
| View order detail | ✅ | Customer info, billing & shipping addresses, line items, current tracking, shipping method |
| Add tracking number | ✅ | Sets tracking_number, orders_status ("Shipped"), and a comment via PUT /orders/{id} |
| View products (paginated) | ✅ | Product ID, SKU (products_model), name, price, stock quantity |
| View product detail | ✅ | Full product with description (HTML stripped, 400-char limit), category, brand, image filename |
| Update stock quantity | ✅ | By internal product_id via PUT /products/{id} with products_quantity. Product IDs are shown in the Products tab. |
| Test connection | ✅ | Hits GET /products?limit=1 — success confirms credentials and API module are working |
products_model values) for stock updates. The product
ID is shown in the Products tab as the ID column. osCommerce-style field names
(products_model, orders_id, etc.) are used throughout the API.
The API key is wrong, or the REST API module is not enabled. Double-check the
api_key value copied from the admin panel. Ensure the API module is installed and
active under Modules → API. Some versions require the API to be explicitly
enabled per-user or per-role.
The REST API module is not installed, or the endpoint path differs from /api/v1/
in your version. Verify the module is installed and check your Loaded Commerce version's
documentation for the correct base path. Also confirm the store URL does not include a
trailing path component beyond the domain root.
Verify the store_url format — it should be the store root, e.g.
https://mystore.com. Do not append /api/v1; EcomCentral adds
that automatically. A trailing slash is harmless and will be stripped. EcomCentral requires a
valid SSL certificate; self-signed certificates will be rejected.
https://your-store.com/api/v1/products?limit=1 in a browser with the Authorization
header set to Bearer {your_api_key} (using a tool like Postman or curl).
A 200 response with a JSON array confirms the API is working.
A 401 means the key is wrong; a 404 means the module is not
installed or the path differs.