Written guide
What you will learn
This Appmint Logistics course connects a delivery request to a zone, an agent and a completed job. We will follow one controlled request across staff and customer views, including an unavailable-area result and a delivery exception.
1. Define where delivery is offered
This retained organization had no zones, agents or jobs. The screen locates the setup tabs; it is not evidence of a route, assigned driver or successful delivery.
The service area, price and vehicle restrictions should be configured before a customer submits a request.
Steps
Open Logistics → Zones → Add Zone to define the controlled area. Enter Name, Title, Code, Status and Description. Define boundaries and inspect Map Preview. Set customer Base Fee, Per Mile, Minimum Fee and Currency, then driver Base Rate, Per Mile and Minimum. Choose allowed vehicles, weight/dimension limits and blocked categories. Set operating schedule, timezone and holidays. Save and reopen. Prepare one pickup/dropoff pair inside the intended area and one outside for the availability test.
Check the result: Area, pricing and restrictions are ready to exercise.
2. Prepare the driver and customer identity
Dispatch requires an eligible agent; the customer request must belong to a real customer identity.
Steps
Open Agents and create/select the controlled driver. Verify Customer/profile, Status, required verification documents, vehicle type/capacity and assigned zone. Save the work schedule and reopen it. Prepare the controlled customer in CRM and confirm their contact details. If exposing a customer booking form, bind it to the supported logistics operation through the actual site/client implementation and verify its submitted record; a generic saved form alone is not a delivery integration.
Check the result: The two identities and the eligible delivery area are explicit.
3. Create and price the first request
The job carries contacts, stops, items and timing. A complete request gives dispatch enough information to proceed.
Steps
Open Jobs → create and select the controlled Customer. Enter pickup/dropoff addresses and contact name, phone and email for each. Add item description, category/type, quantity and weight. Choose Zone, Mode and the scheduled time/window where used. Set required helpers or minimum rating only when appropriate. Choose Get System Price and wait for Calculating... to finish. Inspect base, distance, time, tip and adjustments. If you change the route afterward, the current wizard invalidates the quote and says Route changed. Get System Price again before saving. Recalculate rather than saving the earlier route price. Save once and reopen the returned job. Repeat the outside-area request through the intended client and inspect its actual refusal or available behavior; do not assume a map boundary automatically validates every client.
Check the result: The saved job is complete and the service-area behavior is observed.
4. Dispatch and follow progress
Assignment and progress should be reflected in the same job across dispatch and the agent’s client.
Steps
Reopen the saved job and expand Assignment. Select the correct driver under Assign to Agent (or Reassign to Different Agent when already assigned). Selection immediately requests assignment; there is no separate draft assignment to save later. Wait for Job assigned, then inspect the reloaded job. Alternatively use Broadcast only for your configured matching path and check who actually accepts it. Match the driver identity and job reference before starting the trip. As the controlled delivery proceeds use Start Pickup, Arrive at Pickup, Complete Pickup, Start Dropoff, Arrive at Dropoff, Complete Dropoff and Complete Job in the offered order. Inspect Timeline after each relevant transition and compare the driver/client state. For multiple stops use their individual Arrive and Complete controls. Do not fabricate a physical trip by editing a status value.
Check the result: Dispatch, stop state and agent view remain consistent.
5. Communicate and recover a failed delivery
An exception should stay attached to the request so another staff member can act without reconstructing the story.
Steps
Use Messages on the job for a controlled customer/driver note and verify its actual recipient. Report an issue on the same job with the concrete failure. Inspect the issue entry, then Resolve or Escalate it according to the actual outcome. Attach relevant evidence through the file selector and reopen to verify persistence. If the trip cannot continue use the current-state cancellation path and inspect history. Check any payment and refund consequence separately by transaction reference.
Check the result: The exception, message, evidence and payment outcome remain traceable.
6. Close the delivery and reconcile
Completed delivery, collected customer payment and agent earnings are separate results.
Steps
Inspect the completed job’s stops, evidence and total. Compare the customer-facing state in the actual connected client. Verify any processed payment and its reference rather than setting Paid in a form. Inspect the agent wallet/transactions and intended payout settings. Reopen the job after refresh to confirm the final state. Record any unavailable tracking/customer-notification path instead of presenting the staff screen as proof of customer delivery.
Check the result: The end-to-end request has evidence for delivery and accounting, with unsupported client behavior explicit.
Troubleshooting and recovery
A successful configuration save does not prove the customer workflow. Reopen the exact record, inspect the actual consumer and preserve any error. Check stored state before repeating a create, purchase, message or refund. Keep organization, site, customer and record identifiers aligned across screens. Correct the failing dependency and repeat that verification without disguising an unsupported action.
Your next check
Follow the record through both sides of the workflow. When the intended person can complete the task and the saved result agrees, the setup has evidence behind it.
Limitations and checks
Current Logistics zone, agent and job implementation used. No physical delivery, dispatch, external payment or location test executed. Customer booking/tracking UI varies by connected client; a custom form needs an actual backend binding. Geographic validation, broadcast matching and customer/driver notifications remain live proof.
Appmint Logistics: delivery zones, agents and jobs — supporting guide
Overview
Appmint Logistics brings service zones, delivery agents and jobs into one dispatch workflow. We will create the operating area and agent, price a controlled job, then follow its actual pickup and delivery states with messages and exceptions attached to that job.
Find the dispatch area and check your starting state
Open Logistics → Dashboard. The sidebar's Delivery Zones, Delivery Agents and Delivery Jobs entries open the corresponding Zones, Agents and Jobs tabs inside Logistics Center. Logistics is shown only for organizations enabled for this app (and the deployment's system organizations); the sidebar also requires maker access. Ask your administrator to confirm both organization availability and your role if it is absent. A normal website/storefront account does not automatically become a delivery operator.
This retained screen is an empty organization: Active Zones 0/0, Online Agents 0/0, and no jobs. The Live Map explicitly says Nothing to map yet. Use it to locate the controls, not as evidence of tracking a vehicle. First define where you operate, then an eligible agent, and then a job; a saved agent profile does not by itself establish an online location signal.
flowchart LR
Z["Zone: boundaries, rates, hours"] --> J["Job: customer, stops, items"]
A["Agent: type, capacity, availability"] --> J
J --> T["Assignment and stop timeline"]
T --> E["Delivery evidence"]
J --> P["Customer payment record"]
E --> D["Agent payout review"]Conceptual relationships; payment and payout require their own records and do not follow automatically from a drawn route.
1. Define a service zone
Why this matters
A zone combines boundaries, customer pricing, driver payout and operating restrictions. An address on a map alone does not establish all four.
Follow these steps
Open Logistics → Delivery Zones (the Zones tab) and choose Add Zone. The drawer is titled Create Zone. Enter Name, Title, Code, Status, Type and Description. Set its boundaries and inspect Map Preview. Under Customer Pricing enter Base Fee, Per Mile, Minimum Fee and Currency; configure surge only if intended. Under Driver Payout enter Base Rate, Per Mile and Minimum. Set allowed vehicles, maximum weight/dimensions and blocked categories. Enter Operating Hours, Timezone and Holidays. Save and reopen every section. Test the intended pickup/dropoff against the zone instead of assuming a drawn boundary was saved.
Check the result: The saved zone retains its geographic and operating rules.
2. Register an appropriate agent
Why this matters
Human drivers, machines and third-party providers expose different details. Match the agent type to the actual dispatcher and vehicle.
Follow these steps
Open Agents and choose Add Agent. Choose Agent Type and Customer where applicable, then Status. For a driver inspect profile/KYC documents and verification state; add vehicle Type, Make, Model, Year, Color, License Plate and capacity limits. Assign the zone and work schedule. For a machine use its Name, Manufacturer, Model, Serial, Firmware, battery, home coordinates, payload and range fields instead. For a third-party agent use its Provider, Account ID and API Key, keeping credentials out of captures. Save, reopen and verify the assigned zone.
Check the result: The agent’s actual type and operating constraints match the planned job.
3. Create and price a delivery job
Why this matters
A dispatchable job needs identifiable parties, complete stops, items and a requested timing. Pricing is a service result to inspect, not a number to guess.
Follow these steps
Open Jobs and choose Create Job. Select the Customer and confirm name, email and phone. Enter pickup and dropoff addresses and their contact names/phones/emails. Add items with Description, Type, Category, Quantity and Weight. Choose Zone, Mode and Scheduled At or time window where applicable. Add requirements, helper count and minimum rating only when needed. Use the system-price action and inspect its returned base, distance, time, tip and adjustments. Set the appropriate payment method/status and internal notes. Save once and reopen the job to verify its stops and total.
Check the result: The job persists with the intended stops, items, timing and calculated price.
4. Assign and follow the real delivery stages
Why this matters
Dispatch and delivery progress are separate actions. Each stage should describe something that actually happened.
Follow these steps
Open the job and use its assignment action to choose the eligible agent, or Broadcast when using that matching path. Confirm the resulting assignment. Follow the offered actions in order as the controlled trip proceeds: Start Pickup, Arrive at Pickup, Complete Pickup, Start Dropoff, Arrive at Dropoff, Complete Dropoff and Complete Job. For multiple stops use each stop’s Arrive/Complete controls. After each transition inspect Timeline and the assigned agent’s actual view. Do not fast-forward status fields to mimic a completed trip.
Check the result: The job’s state, stop progress and agent view describe the same controlled trip.
5. Communicate, attach evidence and resolve problems
Why this matters
Messages and issues belong with the job so another dispatcher can follow the history. An issue resolution should include its actual outcome.
Follow these steps
Open Messages on the job, send a controlled operational message and verify its visible thread. In Issues report the actual controlled problem and inspect its recorded entry. Use Resolve or Escalate on that specific issue according to the intended outcome. Add the relevant image through the file selector and reopen to verify its saved path. Inspect tracking and delivery evidence before calling the job complete. If a job must be cancelled use its current-state Cancel action and verify the resulting history and payment implications separately.
Check the result: Communication, evidence and issue state stay attached to the correct job.
6. Adjust pricing, payments and agent payout
Why this matters
Changing a quoted amount and collecting it are different actions. Likewise driver payout is separate from customer payment.
Follow these steps
Open the saved job’s pricing controls. Add a justified controlled adjustment, inspect the resulting total and remove a disposable adjustment to verify recalculation. Use the payment process only with the intended method and controlled account; inspect the returned transaction rather than setting Paid manually. Open the agent’s payout settings and inspect method, frequency and bank details privately. Review wallet transactions, credit/debit and request-payout controls without making an unnecessary monetary adjustment. Compare the job payment and agent accounting records by reference.
Check the result: Customer pricing, actual collection and agent payout evidence remain distinguishable.
Troubleshooting and recovery
Keep the exact record and operation visible when reading an error. Inspect persisted state before retrying a write; a timeout does not prove nothing happened. Correct the specific cause and verify the resulting record and consumer independently. An enabled feature, successful configuration save or administrative status is not proof of an external delivery, access boundary or money movement. Preserve unsupported behavior rather than simulating success.
Next steps
You can now use the module’s records and controls in context, and check the result at the point where it matters. Return to the relevant chapter for the advanced path and its verification.
Limitations and checks
Current zone, agent and job wizard source inspected, including status actions, issue/message handlers and pricing/payment actions. No dispatch, location tracking, provider charge or physical delivery executed. Map/geocoding, broadcast eligibility, agent client behavior and accounting require controlled live proof. A configured payout frequency is not evidence of a running scheduler.