> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/b2b-bulk-order/features/quick-order-form.md).

# Quick Order Form

A Quick Order Form is a table of products that lets a customer search, set a quantity for as many items as they want, and add them all to their cart in one action. Unlike Variant Table and Collection Quick Order, it doesn't attach itself to a page automatically — you place it using a shortcode (see [Add the form to a page](/b2b-bulk-order/getting-started.md#add-the-form-to-a-page)).

Manage forms from **Quick Order** in the app navigation. The list shows each form's name, status (Active/Draft), shortcode, display pages, customer visibility, and products, with bulk actions to duplicate, activate, set to draft, or delete.

{% hint style="info" %}
Deleting a form asks you to confirm: *"Are you sure you want to delete the selected quick order form(s)? This action cannot be undone."*
{% endhint %}

<figure><img src="/files/jrbrXOfonnjP9XYtkHc5" alt="Quick Order Form list screen"><figcaption><p>Quick Order Form list</p></figcaption></figure>

## Choosing products

On the **Products** tab, pick one of three modes:

* **All products** — every product in your catalog.
* **Specific products** — hand-pick individual products.
* **Specific collections** — include everything in one or more collections.

{% hint style="warning" %}
If you choose Specific products or Specific collections without selecting anything, you'll see **"Select at least one product"** or **"Select at least one collection"** when you try to save.
{% endhint %}

## Customizing the form

The **Customize** tab controls what shoppers see and how the table behaves.

### Header

Set a **Title text** and a **Description** (up to 200 characters) per language.

### Search & sort

Toggle **Show search** and **Show sort**, and pick which sort option is selected by default. Customers can choose from:

* Sort: Recommended
* Name: A to Z
* Name: Z to A
* Price: Low to High
* Price: High to Low
* Newest first
* Oldest first
* Best selling

### Table columns

Pick which columns appear, and drag to reorder them:

| Column                  | Shown to customer as |
| ----------------------- | -------------------- |
| Product / Product image | Image                |
| Product name            | Name                 |
| Product price           | Price                |
| Compare at price        | Compare at price     |
| Product SKU             | SKU                  |
| Product vendor          | Vendor               |
| Product type            | Type                 |
| Product stock           | Stock                |
| Quantity                | Quantity input       |
| Action                  | Add button           |

Turn on **Separate variant rows** to list each variant as its own row instead of grouping them under the parent product.

{% hint style="info" %}
Quick Order Form quantity fields are capped at each item's available stock — there's no minimum order quantity or "multiple of X" rule here. For those rules, use [Variant Table](/b2b-bulk-order/features/variant-table.md#advanced-restrictions).
{% endhint %}

### Pagination

Choose **Pagination** or **Load more**, and set **Products per page** (10, 20, 40, 50, or 100). The value must be between 1 and 250.

## Letting customers upload an order file

Turn on **Enable file upload** — *"Allow B2B customers to upload order files instead of entering quantities manually."* When on, choose which file types to accept from: CSV, XLSX, PDF, JPEG, PNG.

On the storefront, customers open the **Bulk order** button to get an upload modal:

* **CSV / XLSX** are read directly in the browser. The file needs a `SKU` column; a `Qty` or `Quantity` column is optional (rows without one default to a quantity of 1).
* **PDF and images** (JPEG, PNG) are sent to an AI-powered parser that reads the order sheet and extracts SKU/quantity rows automatically.

A **Use demo file** button lets the customer try the feature with a sample file before uploading their own. Matched rows are shown next to unmatched SKUs so the customer can review before confirming with **Add to cart**.

<details>

<summary>Customer-facing messages during import</summary>

* "Analyzing image…" — while an image/PDF is being processed
* "{{matched}} of {{total}} row(s) matched a product in this list."
* `SKU "{{sku}}" not found`
* "This file type isn't supported for automatic import yet. Please use a CSV or XLSX file."
* "Couldn't read this file. Please check the format and try again."
* "No matching SKU/Quantity rows were found in this file."
* "We couldn't read this image automatically. Please try a CSV or XLSX file."
* "{{count}} item(s) added to your order."

</details>

<figure><img src="/files/f5lRZSrhmWVL70wPibia" alt="Bulk order file upload modal"><figcaption><p>Bulk order upload modal</p></figcaption></figure>

## Style and visibility

Layout, colors, and Custom CSS are covered in [Design & Custom CSS](/b2b-bulk-order/features/design-and-custom-css.md). Who sees the form and on which pages is covered in [Customer & Product Targeting](/b2b-bulk-order/features/customer-and-product-targeting.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.samita.io/b2b-bulk-order/features/quick-order-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
