An example bale.
Every bale, accounted for. Row, rack, mass and merchant.
SwiftlyWarehouse runs a tobacco warehouse from the truck at the door to the cartons back from the factory. Bales are scanned against the floor's shipment file, weighed again and placed by row and rack, then blended to order or dispatched, with each merchant's leaf accounts kept apart.
Follow a bale
One record, from the truck to the factory
Each step adds to the same record, so a bale's whole story is one line of the stock report.
The steps move on by themselves. Press one to stay on it.
What it catches
Where a warehouse loses track, and what happens here
Paid for, and not here
A ticket on the shipment file that nobody has scanned stays on that shipment's pending list, ready as CSV or PDF. With SwiftlyERP linked, it shows as tobacco bought that has not reached the warehouse.
Here, and not on the file
A bale the shipment file does not know is refused at the scanner, and can go on the holding list with its row and rack. It stays out of stock until someone moves it in.
Scanned twice
A ticket already captured is refused, and so is one already dispatched. A ticket number can only be on one bale.
Lighter than its ticket
The re-weigh sits beside the ticket mass on every bale, and each shipment report adds up the variance.
Changed, and nobody knows why
A change of grade, price, mass, ticket or place keeps who made it, when, and what it was before. Price and grade changes have logs of their own.
A blend off its target
A blend dispatch knows its green target. Scans past the target and its allowance are refused, and it will not close short of the target. The blend's containers are checked against the dry mass expected.
Many merchants, one warehouse
Each merchant sees its own bales
One warehouse can hold tobacco for several merchants. Each merchant's link reads only the bales bought under its buyer codes, and what follows from them.
- Its dispatches, returns, adjustments and blending use
- On a truck carrying several merchants' bales, its own share
- A key of its own, which you can rotate or revoke at any time
- The operator's own link reads the whole warehouse
Press a merchant to see what its link reads
An example floor: rows down the side, racks along the top.
The parts
Take the parts your warehouse runs
Each part is switched on for your company on its own. Switching one off keeps its data, and switching it back on brings it back.
Green warehouse
- Shipments and receiving
- Auction and contract bales
- Holding and relocation
- Re-ticketing, grade and price changes
- Floorlay and green stocks reports
Dry warehouse and dispatch
- Dispatch to the factory
- Factory returns
- Processed tobacco and cartons
- Invoicing source files
- Dry stocks reports
Needs Green warehouse
Blending
- Blend catalogue, customers and orders
- Allocating bales to an order
- Blend dispatches
- Receiving, and container trace
Needs Green warehouse
SwiftlyScale
- A desktop app at the scale
- Weighs contract bales straight into the warehouse
- Reads the mass from the scale
- Queues bales when the connection drops
Needs Green warehouse
Core, with every warehouse
Sign-in, the dashboard, buyers and grades, users and roles, rates and season settings, and backups.
Alone or linked
It runs on its own, and links when you want it to
On its own
Your warehouse at its own address, with its own database, settings and files. It needs none of the other Swiftly systems to run.
yourcompany.swiftlywarehouse.comWith the rest of Swiftly for Tobacco
The floor's shipment file tells the warehouse which contract bales are on the truck, so receiving has something to check them against.
Stock, intake, bales, blending and factory dispatches show in the ERP, and it checks that every bale arrived as it left the floor. The link only reads.
See it on your own floor
Tell us how your warehouse runs, and we will show you the rest.
We set up your warehouse at your own address. A demo takes half an hour on WhatsApp or in person.
