Pallit is a free, open-source warehouse management system that runs on your local network. Manage inventory, employees, storage, shipping, time records, payroll preparation, and basic bookkeeping in one easy-to-use workspace—without subscriptions or complicated infrastructure.
Pallit is a free, open-source warehouse management application that brings inventory, employees, shipping, time records, payroll preparation, and basic bookkeeping into one local workspace. One computer hosts the application and stores its data. Employees connect through a browser over the same reachable Ethernet or Wi-Fi network.
The workflow starts with a simple setup and grows with the operation. A small team can begin with inventory and basic location labels, while a more structured warehouse can configure zones, crews, permissions, and outbound procedures.
1. Start the application and create the workspace.
The owner installs Node.js 24 or newer, downloads Pallit, and double-clicks its launcher. On the first launch, they create an administrator account and name their warehouse. They can explore a sample operation or start with an empty workspace.
The administrator can create additional warehouses, each with its own inventory, employees, locations, and operational records.
2. Configure the warehouse’s operations.
The administrator chooses which activities the warehouse performs, such as receiving, storage, picking, or shipping. A shipping-only operation can keep its setup focused on shipping.
Pallit supports gradual setup: users can start recording inventory before they have a detailed floor plan.
3. Create storage zones and location labels.
Users can organize space into general storage, hazardous storage, cold storage, or staging zones. Each zone can have a pallet capacity and an optional position on the warehouse grid.
For example, a warehouse could create an HM zone with a capacity of 200 pallets, then add locations such as HM-01 and HM-02. A smaller operation could simply use labels such as Back Room or Shelf A.
Inventory receipts and transfers check the configured capacity and storage category. Hazardous-material categories provide basic placement controls; they do not calculate chemical compatibility.
4. Add employees, job roles, and teams.
Managers create employee records with names, job titles, departments, and shifts. They can define roles such as picker, lumper, forklift driver, inventory specialist, or outbound lead.
Employees can then join teams with a designated lead and assigned work locations. For example, an outbound crew might work in staging, while a receiving crew handles unloading and put-away.
Employee records can exist without sign-in accounts, allowing supervisors to attribute work to employees who do not use the application themselves.
5. Create accounts and assign permissions.
Administrators create individual sign-in accounts and choose which warehouses each person can access. They can use built-in access roles or create custom permission sets.
Job titles and application permissions are separate. A forklift driver’s job title describes their work; their access role determines whether they can move stock, adjust counts, manage orders, or view reports.
Payroll and finance require separate permissions. An account can also be linked to an employee record for submitting and viewing that employee’s own time.
6. Build or import the inventory catalog.
Users create inventory items with SKUs, names, categories, units of measure, units per pallet, storage requirements, and reorder points.
Existing inventory can be imported from a CSV file. Users map the source columns, review the preview, and submit the import. Imported quantities are recorded as additional receipts, so importing the same quantities again adds them again.
Stock is tracked by item, location, and lot, giving users visibility into both total inventory and where it is stored.
7. Record incoming trucks at the gate.
A guard or receiving employee records the driver, carrier, truck, bill of lading, freight description, expected pallet count, and other available load details as the truck arrives.
The load progresses through At gate → At dock → Complete → Departed. Dock assignment helps prevent two active loads from occupying the same dock.
The information becomes available to authorized colleagues without requiring someone to re-enter the guard’s notes later.
8. Receive inventory and record its placement.
Receiving staff enter the quantities actually received and select the destination location. They can attach lot, BOL, truck-load, and performing-employee references.
Pallit checks storage requirements and capacity before saving the receipt. Successful receipts increase stock and create a movement record.
Truck status and inventory quantities are separate: marking a truck complete does not automatically receive its expected freight.
9. Coordinate work and internal movements.
Supervisors create operational tasks and assign them to employees. Workers or supervisors update task progress as work proceeds.
Inventory transfers record movement between locations. Physical-count adjustments require appropriate permission and a reason. Each movement preserves the quantity, origin, destination, time, performing employee, and account that recorded it.
The Department hub provides shared updates and urgent handoffs between receiving, shipping, inventory, and other departments.
10. Create and process outbound orders.
An outbound order identifies the customer, requested SKUs and quantities, destination, requested ship date, and optional team, source location, or truck load.
The warehouse can define its own sequence of outbound stages—for example, Queued → Picking → Packing → Ready to ship. Existing orders retain the workflow they were created with.
Reserving inventory assigns available stock to the order. Reserved units are protected from other shipments, transfers, and count reductions. If the full order cannot be reserved, the reservation attempt leaves stock commitments unchanged.
Staff advance the order through its stages, then confirm shipment with a BOL or dispatch reference. Confirmation deducts the reserved quantities and creates the corresponding movement history. Cancelling an open order releases its reservations.
11. Submit and review employee time.
Employees with linked accounts can submit their own daily time. Authorized managers can record time for the team.
Each entry includes the work date, total shift minutes, unpaid breaks, and optional team, location, and notes. A reviewer approves the entry or returns it for correction.
These are entered time records; the current workflow does not provide an automatic clock-in kiosk.
12. Prepare hourly and salaried payroll.
Authorized users configure employee compensation and the operation’s pay rules.
- Hourly employees: pay is calculated from approved paid time using the configured hourly rate, workweek, weekly overtime threshold, and multiplier.
- Salaried employees: each run uses a configured gross amount for one complete pay period. Annual conversion and partial-period prorating are manual.
A draft pay run captures the applicable rates, time, and rules. Reviewers can add earnings or manual deductions with an explanation. Overlapping pay runs for the same employee are blocked.
Approval locks the run and records payroll expense and amounts payable. After payment is made externally, an authorized user records its date and reference. Pallit supports payroll preparation and recordkeeping; it does not calculate statutory taxes, file returns, or transfer money.
13. Record invoices, income, and expenses.
Finance users can create customer invoice drafts, optionally linked to outbound orders. Issuing an invoice records revenue and an amount receivable.
Full or partial payments received elsewhere can then be recorded against the invoice. Users can also record operating income, expenses, opening balances, and manual financial adjustments.
Entries are stored in a balanced journal. The resulting balances reflect what has been recorded in Pallit, rather than a live connection to a bank account.
14. Review, export, and back up the operation.
Authorized users review inventory balances, movement history, outbound progress, employee time, pay runs, invoices, and recorded financial activity.
Data can be exported to Excel, individual CSV reports, or structured JSON. Export visibility follows the user’s permissions. CSV imports and the documented HTTP API provide integration options for other software.
Administrators can download a complete database backup. The host computer must remain running for connected employees to use the application; when it is stopped, the saved data remains available for the next session.