Handle inbound and outbound orders
Use purchase orders for incoming supply and sales orders for customer demand, with the receiving or fulfilling store on the commercial document.
Explore Sales OrdersMovement-level traceability
Keep the warehouse quantity tied to its source document.
Receipts, issues, transfers, returns, and corrections post signed movements. Each posted line records the date, product, store, direction, quantity, cost, and the document that caused it, while on-hand is calculated from the ledger rather than maintained separately.
Post the physical movement
Receive, issue, transfer, return, adjust, or count goods so the signed movement ledger remains the source for stock on hand by product and warehouse.
Explore InventoryWork consignment questions as tickets
Log a requester, priority, category, assignee, and conversation; triage the case, request information when needed, and close it with a reusable solution.
See the ticket flowWarehouse handoffs
Move the paperwork with the goods.
The order, inventory document, movement line, and delivery note stay separate because they answer different operational questions, but their references keep the trail connected.
- 1Operations
Record the order
Capture the customer or supplier, products, quantities, dates, and store.
- 2Warehouse
Post the movement
Confirm what physically arrived or left before the ledger changes.
- 3Dispatch
Create the delivery note
Copy the posted issue into a quantity-only customer document.
- 4Back office
Bill and answer
Issue invoices, record payments, and work service tickets around the transaction.
Dispatch in practice
Give the customer a delivery record without exposing prices.
A delivery note records the customer, dispatching store, date, optional employee, sales order, goods issue, tracking number, and quantity lines. The normal path creates it from a posted goods issue so the dispatch data does not need to be typed twice.
- Automatic delivery-note number
- Customer and dispatching store
- Sales-order and goods-issue links
- Product and quantity lines
- Optional employee and tracking number
- Printable Bulgarian or English document
Two operational views
Follow quantities and customer questions without mixing them together.
Warehouse records answer what moved and why. Service tickets hold the conversation when a customer, supplier, or employee needs an answer.
Orders, receipts, issues, transfers, returns, counts, and on-hand reports by store.
Ticket priority, assignee, conversation, status, escalation flag, and recorded solution.
Movement, stock value, order, invoice, payment, and ticket reports.
Linked module and flow documentation for the people maintaining the setup.
The wider logistics back office
Keep orders, stock, service, and finance in one suite.
The Logistics solution combines warehouse movement records with the customer, supplier, people, billing, and accounting work around them.
StoresMaintain warehouse names, codes, addresses, companies, managers, and status.Inbound ordersOrder goods from suppliers for a chosen receiving store.Outbound ordersConfirm customer demand before goods are issued.Service deskWork requester conversations and reusable resolutions.BillingIssue invoices and follow balances and customer payments.AccountingUse the chart of accounts and journal alongside operations.
Current scope
Shipments, carrier management, freight rating, fleet records, and route planning are not currently modelled. Delivery notes are the only transport-shaped document in the documented solution.
A configurable starting point
Adapt the warehouse and service records to your operation.
BusinessIntents can adapt documents, fields, approvals, reports, or business areas on request when the standard Logistics solution does not match your operating model.
Try BusinessIntentsDecision-stage answers
Logistics FAQs
Who is the Logistics solution designed for?
It is designed for operators that manage warehouses and stock movements, handle inbound and outbound orders, create delivery notes, work service tickets, and keep invoicing and accounting records around those operations.
How is stock on hand calculated?
On-hand is the live sum of signed movement quantities per product and store. The ledger records the source document behind each posted receipt, issue, transfer, return, or adjustment.
Can a goods issue create a delivery note?
Yes. The delivery note can copy the customer, store, sales order, and quantity lines from a posted goods issue while retaining a link to it.
Does the solution include a service desk?
Yes. Tickets support triage, assignment, requester conversations, internal notes, information requests, escalation flags, resolution, and a reusable solution record.
Does it plan routes or manage carriers?
No. Shipments, carriers, freight rating, fleet operations, and route planning are outside the currently documented solution.
Can the solution be adapted?
Yes. Documents, fields, approval paths, reports, and complete areas can be adapted on request.
Follow one dispatch
See the order, warehouse movement, and delivery record together.
Use a real outbound process to review where the documented workflow fits and where your operation needs a different record or handoff.