> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/~/changes/1509/supplyd-lite/about-supplyd-lite.md).

# About Supply'd Lite

Supply’d Lite offers a streamlined, user-friendly solution for managing purchase orders, making it ideal for small businesses seeking improved efficiency without the complexity of advanced systems.

**Supply’d Lite** is a free simplified version of the full Supply’d platform, designed for smaller teams or businesses with basic purchase order management needs. It offers purchase order management, without the complexity of advanced features like automation, integrations, or multi-location controls. Supply’d Lite is ideal for businesses looking to improve efficiency and accuracy in their ordering while keeping things straightforward and easy to use.

Here’s a quick comparison of features in Supply’d Lite versus the full Supply’d platform:

| **Feature**                  | **Supply’d Lite**                        | **Full Supply’d**                                            |
| ---------------------------- | ---------------------------------------- | ------------------------------------------------------------ |
| **Inventory Management**     | ❌ Not available                          | ✔️ Advanced tracking with batch/expiry/location              |
| **Purchase Orders**          | ✔️ Create, send and manage orders        | ✔️ Full order workflows with custom statuses                 |
| **Sales Orders**             | ❌ Not supported                          | ✔️ Full order workflows with custom statuses                 |
| **Multi-Location Support**   | ❌ Single location only                   | ✔️ Supports multiple warehouse and store locations           |
| **Integrations**             | ❌ Not available                          | ✔️ Integrates with platforms like Xero, Square, Shopify etc. |
| **Automation Tools**         | ❌ Manual processes only                  | ✔️ Automatic pick scheduling, syncing, and more              |
| **Cluster Picking**          | ❌ Not supported                          | ✔️ Supports cluster and bulk picking workflows               |
| **Reports & Analytics**      | ❌ Not included                           | Advanced reporting and custom dashboards                     |
| **Packing Stations**         | ❌ Not included                           | ✔️ Full support for packing workflows                        |
| **User Roles & Permissions** | Limited control for one additional user. | Detailed role and permission management for unlimited users. |
| **Best For**                 | Small teams, simple operations           | Growing or complex businesses with advanced needs            |

***

### Creating Your Account

To create your account go to <https://app.supplyd.co/register/>.

Follow the guidelines in the [Creating Your Account](https://help.supplyd.co/~/changes/1509/getting-started/quickstart.md) document to create your account.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.supplyd.co/~/changes/1509/supplyd-lite/about-supplyd-lite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
