What was a pain in Unleashed, and how Pallas handles the same thing.
Every spreadsheet had to be reformatted into Unleashed's exact import template — columns renamed and reordered, item codes lined up — before it would accept the data.
You hand it the spreadsheet as-is. It reads whatever format it's in and loads the items and stock.
Each product had to be matched to its Unleashed item number by hand — wrong names, missing numbers, and a separate list for the ones that didn't match.
It matches the products for you and only asks about the few it genuinely can't place.
When H‑E‑B's orders arrived through their platform, Unleashed had never heard of H‑E‑B's part numbers — the integration stalled until a consultant emailed asking for a spreadsheet mapping every product by hand.
Connecting a retailer's platform (TOE, TrueCommerce, their portal) asks for their part numbers up front — paste the list once and their orders import themselves, cases converted to units. Anything unrecognized parks loudly instead of guessing.
The day's production had to be entered by hand every day, and it wouldn't accept a past date.
Record a production run in one step, for any date. It subtracts the ingredients, creates the finished product, and records the cost.
It can't create pallet numbers at all — we had to build a separate Chrome extension just to generate them and paste each one in by hand.
It assigns the lot and pallet numbers automatically when you receive a shipment, and prints the label.
A product's label prints blank unless you first switch on "batch tracking" in that product's settings — and nothing tells you, so you only find out when a blank label comes out of the printer.
It checks that setting for you, tells you what's missing before you print, and turns it on.
Only one tracking field per line, so the lot number and the pallet number had to be crammed into a single number.
Lot and pallet are two separate fields, both printed on the label.
If the on-hand count was off, it wouldn't let you record a production run you'd actually made.
It shows what it thinks you're short and lets you record the run anyway — keeping the mismatch visible to fix — or correct the count first.
Purchase orders lived in QuickBooks, so you exported them, re-entered them in Unleashed, received against them, then reconciled the two systems.
Orders, inventory, and the books are one system that syncs to QuickBooks on its own — nothing gets re-entered.
Getting a purchase order to a supplier meant clicking through screens to send it out.
One click emails the purchase order — or a PDF of it — straight to the supplier.