The TITOL WMS Guide is available to signed-in users. Sign in, then return to this page.
Reports / Projects / TITOL WMS
What the WMS is for, how a shipment moves from your notice to your customer, what you can do yourself, and what we promise you will always be able to see.
Every unit accounted for, every touch logged, every client in the know.
TITOL WMS is a job-centric warehouse system built for artist and brand merchandise. Intake, storage, fulfilment and billing live in one place, the job is the hub, and every physical movement links back to its record. It is not a report we send you. It is the system we run the floor from, and you have a window into it.
// Merch moves fast and in odd shapes: tour splits, seeding, box sets, returns. The system is designed so that speed never costs you a paper trail.
Seven steps, in the order they happen. The badge says who acts. Every step leaves a record you can open.
// A job can also start from an email or a phone call. Either way it ends up in the same place: one job, with everything attached.
Four things you can do without emailing anyone. Each opens inside the WMS at the address shown.
Reports cover intakes, orders and shipments over any period. Project reports compile a whole program, such as a tour leg or a box-set run, into one page with reconciliation, open items and the source files attached.
Reply to any email we send about a job and it files onto that job automatically. The thread, the files and the billing sit together, so the answer to "what happened with this" is always one place.
Transparency here is not a summary we write for you. It is the same records, opened to you as they are created.
| What | When it appears | Where |
|---|---|---|
| On-hand units | The moment intake finishes. Deducted the moment a pick runs. | Brand portal › Inventory |
| Receiving record | When the dock confirms a delivery: counts, signed packing list, photos, discrepancy flag. | The job for that delivery |
| Movements | Every intake, move, pick and reversal, with who and when and the order it belongs to. | Reports › Movements, and on the job |
| Packing lists | For every shipment out, filed on the job as a PDF. | Job › Deliverables |
| Tracking | Recorded on the shipment when booked. Exceptions are flagged. | Job › Shipments |
| Invoice lines | Each line is a real task with real units and the rate that applied. Comped work is shown at value, then zeroed. | Invoice on the job |
| Project reports | Compiled at the end of a program, or on request. | Reports › Projects |
// Corrections are visible too. When we reverse a pick or fix a count, the original stays and the correction is logged next to it. We do not edit history.
Five rules the system enforces on us. They are the reason the promises above hold.
The identifiers you will see on records and in emails. Hover any dotted term on this page for the same definitions.
| Term | Looks like | Meaning |
|---|---|---|
| JOB-#### | JOB-3875 | A job. The number in every email subject about that work. Reply and it files itself. |
| ASN | ASN-00042-YEAT | Advance Shipping Notice, created by a Receiving Order. What we expect before it arrives. |
| REC | REC-00118 | A receiving record: what actually arrived, counted and photographed at the dock. |
| Box ID | YEAT-260910-47 | Brand, date received (YYMMDD), carton sequence. On the carton label and every movement. |
| PLT-### | PLT-036 | A physical pallet. Where the carton lives. |
| ORD-##### | ORD-16668-YEAT | An order request from you, or the pick order we ran to fulfil it. |
| SHP-##### | SHP-00145 | A shipment out, with its packing list and tracking. |
| INV-##### | INV-10407 | An invoice, built from job lines. |
| Feasible date | Sep 14 | The earliest date we can reasonably ship a request, computed when you submit it. Earlier is a rush. |
| Discrepancy | flag on a REC | Counts or condition did not match the paperwork. Noted, photographed, and raised with you. |
Reply to the email that mentions its JOB number. Your reply lands on the job, with any attachments, and the person working it sees it there.
Use Feedback inside the WMS, or write to us directly. Access requests for new team members go through the sign-in page and are approved by us.
// This guide is versioned with the WMS. When a step changes, this page changes with it.