---
title: What is not yet supported on Wholesale Handler
Metadescription: The plan limits, the features still to come, and the things Wholesale Handler will not do - payments, accounting sync, stock control, routing and POS.
author: Dan Edwards
author_role: Founder
author_url: https://danedwardsdeveloper.com
author_linkedin: https://www.linkedin.com/in/dan-edwards-developer
published: 2026-08-26
---

Token estimate: ~980

# What is not yet supported on Wholesale Handler

Wholesale Handler is the ordering layer between you and your trade customers, so the back office is out of scope on purpose. Payment processing, accounting sync, delivery routing, stock as the system of record and point of sale will not be built. Credit notes, automatic invoicing and deposits are not built yet and sit on the [roadmap](https://wholesalehandler.com/roadmap). Everything else is a plan limit, and plan limits can be raised.

By **[Dan Edwards](https://wholesalehandler.com/about)**, Founder.

## The plan limits

| Limit | Ceiling |
| --- | --- |
| Products | 500 |
| Customers | 50  |
| Price lists | 20  |
| Order profiles | 20  |
| Active standing orders, per customer | 10  |

They exist to keep a single flat plan viable rather than to fence you in. None is a technical ceiling, and any of them can be raised for an individual business, so email Dan before assuming a larger operation will not fit.

One sign-in per business is the exception, and it is a build rather than a policy - colleagues cannot yet have separate accounts of their own.

## What will not be built

| Not built | What happens instead |
| --- | --- |
| Payment processing | Both sides record and confirm payments; the money does not pass through Wholesale Handler |
| Accounting integrations | Finalised invoice lines [export to CSV](https://wholesalehandler.com/articles/how-data-export-works-on-wholesale-handler) for any package |
| Stock as the system of record | Optional per-product counts; a product left untracked has no stock limit at all |
| Recipe costing and batch scheduling | Orders roll up into a [production schedule](https://wholesalehandler.com/articles/how-production-schedules-work-on-wholesale-handler) of what to make |
| Point of sale | Nothing - every buyer is a trade account you set up |
| Public sign-up and checkout | The optional storefront shows your products and takes no orders |
| Delivery routing and tracking | Delivery dates and cutoffs; planning the van is yours |
| Quotes | A per-customer price list settles the price before the order is placed |
| Reading orders out of emails and voicemails | The customer places the order themselves |

## What is not built yet

-   **Credit notes.** A finalised invoice cannot be credited for a return or a short delivery. Adjustment lines on a draft are the only correction.
-   **Automatic invoicing.** You raise each invoice from your processed, uninvoiced orders. Nothing is billed on a schedule.
-   **Deposits and prepayment.** A seasonal pre-order is a delivery date plus a cutoff. No money is taken or tracked up front.
-   **Country holiday packs.** Every closure is added by hand.
-   **Scheduled changes.** A new cutoff or a dropped delivery day applies the moment you save it. You cannot date one for next month.

## Q&A

**Q: Is EDI supported?**
A: No, and it is not planned. Orders arrive because your customer placed one in the portal, not because their system sent a document to yours.

**Q: How do I know when something on the roadmap has shipped?**
A: The roadmap opens on what landed in the last 90 days, above what is being built now, what is queued next, and what is still being considered.

**Q: My customers order by phone and WhatsApp and will not sign in. Is that supported?**
A: Yes. A managed customer is a record you hold rather than an account they use, and you place their orders and email their invoices yourself. Nothing about the rest of the system changes.