Flows
A flow is a whole job done through the API, from the first call to the last: ordering stock, selling it, shipping it, getting paid. Each step says why it exists, the call it makes, and what it records.
Every flow here is also a test. The platform's end-to-end suite runs each one against a real stack, so the calls and answers shown are ones that work.
- Procure to pay
Buying stock and paying for it: raise a purchase order, authorise it, receive the goods, then settle the supplier invoice at the price actually charged.
- Ordering stock in, and counting it when it lands
Order stock in, receive it, and name tracked units.
- Running more than one location
Open a second location, move stock to it, and see what
fulfillablechanges. - Order to cash
Sell stock and get paid: quote, place the order, pick, pack and ship a parcel, take the payment, invoice it and refund part of it.
- Store credit and gift cards
Balances customers hold, as tenders: give a customer store credit and take it back, issue a gift card and look its code up, pay an order with the card, refund part of it back onto the card the money came from, and stop the card.
- Journal an additional cost on an order
A cost the order incurred that no other command records — a courier to redeliver, a customs broker's fee — journalled by hand on the sales order or the purchase order it belongs to: an amount, a reason and the chart account it is charged to.
- Selling stock you do not have yet
Take an order for more than you have, and see it fill when stock arrives.
- Bulk import from a spreadsheet
Bring a spreadsheet of existing data in: upload, preview, map the columns, apply.
- What happens when you get it wrong, or send it twice
What a call does the second time, and what a refusal looks like.
- Curate a channel catalog
Deciding what one selling view is allowed to see: open a catalog for a channel (an Australian online store, a POS register, a B2B company), include a product in it, price its SKU in the catalog's currency, then read the resolved view the channel consumes.
- Pay reps commission
Setting up what reps earn: when commission is earned and by whom, a commission group with its base rate, a rep in it, a catalog's own rate for one SKU and that group, and the catalogs the group's reps sell from.
- Keeping the chart of accounts
Add an account, point a SKU at it, and see why an account in use cannot be removed.
- Attach a photo to a SKU
Files — photos, spec sheets, drawings — hang off SKUs and products.
- A person, a supplier, and a right-to-erasure request
The CRM is the one registry every picker reads: a purchase order names a supplier by id, an order names its customer by id, and neither holds a name of its own.
- Build, save and run a report
Save a report, run it, and trace a figure back to what was recorded.
- Read the dashboard and tidy it
The admin's home screen is an analytics strip — sales, orders, units and average order value against the period before — over cards a person may dismiss for themselves.
- Pack parcels into your boxes
List the boxes each location packs with, and let Manifold choose the boxes for a parcel.
- Print labels at a site
Add a site's label printer and print a SKU's shelf labels on it.
- Send mail from your own domain
Send email to customers and suppliers from your own domain, and see the record of each message.
- Send text messages under your own name
Send text messages to customers and suppliers under your own sender ID, and see each one in the same record as your mail.
- Design your own emails
Design the emails your customers and suppliers receive — invoices, quotes, order confirmations and purchase orders — in react-email's own components, or start from one of Manifold's.
- Share a quote your customer can accept
Give your customer a page for their quote, in your brand, that they open from a link and accept or decline with no account.
- Serve your customer pages on your own domain
Have your customers open their quotes, orders, invoices and tracking on a subdomain of yours —
orders.yourstore.com— instead of Manifold's address. - Run beside your old system, then go live
Run Manifold beside your old system, then go live.
- Page through the order book, arranged your way
The orders screen is a page of the book at a time, newest first, with a tab per status: the service filters, counts and pages, so a business with thousands of orders reads them as quickly as one with ten.
- Set up a station and unlock it with a PIN
A station is a device kept signed in to one job — pick & pack, receiving, a stocktake, the register — at one site, unlocked by the people who work it with their own station PIN.
- Open the books with a stocktake
Every set of books begins with the stock counted and valued.
- Close the books on a year
Once a financial year is closed, what was done in it is final.