Coordinating the Delivery Desk: Evidence from 110 Current Vacancies in Logistics Coordination and Delivery Operations
The complete open archive - a visually reviewed PDF, the rights-reviewed 110-row dataset, coding summary, quality record, methods appendix and data dictionary - is preserved at Zenodo DOI 10.5281/zenodo.22144825. The direct public PDF is available here.
Research report
Research date: 28 August 2026
Language: English
Sample: 110 current, deduplicated public vacancies
Course context: Professional Certificate in Logistics Coordination and Delivery Operations
Abstract
This report examines what employers ask people to do when they coordinate the movement of physical goods from an authorized shipment release through pickup, transport, delivery evidence and operational closure. The study uses a point-in-time purposive sample of 110 current public vacancies retrieved on 28 August 2026. The accepted corpus contains 110 unique individual vacancy URLs and 110 unique deduplication keys across 101 employers, 15 countries and ten source platforms. It is not a census or a probability sample.
The strongest recurring signals were stakeholder and customer communication, observed in 105 vacancies; milestone, estimated-time-of-arrival and delivery visibility, observed in 103; delay and service-exception recovery, observed in 94; carrier, driver and delivery-partner coordination, observed in 85; pickup, delivery, dispatch and appointment coordination, observed in 78; KPI and status reporting, observed in 68; and operational documents and records, observed in 66. Counts are non-exclusive and describe only this accepted sample.
The evidence supports a practical learning design built around a repeated delivery-control cycle: receive a release handoff, coordinate bookings and appointments, maintain live visibility, triage and recover exceptions, communicate accurate updates, reconcile delivery evidence, review service data and close the operating record. The report also identifies clear limits. Warehouse execution, carrier contracting, driver operations, customs decisions, dangerous-goods procedures and jurisdiction-specific compliance instruction require separate ownership or specialist review.
Executive summary
The evidence supports five central conclusions.
-
Communication and visibility form the operational backbone. Stakeholder communication appeared in 105 of 110 vacancies (95.5%), while milestone, ETA and delivery visibility appeared in 103 (93.6%). The coordinator is repeatedly positioned as the person who keeps the operating picture accurate and usable across customers, carriers, drivers, warehouses, 3PLs and internal teams.
-
Exception recovery is routine work, not an edge case. Delay and service-exception recovery appeared in 94 vacancies (85.5%). The principal coded decision—recover, reroute, reschedule, hold or escalate—was observed explicitly in 40 vacancies (36.4%). Public vacancy text often compresses decision authority, so this count should be read as a minimum observed signal, not as the full amount of judgement used in practice.
-
The role coordinates execution through other parties. Carrier, driver and delivery-partner coordination appeared in 85 vacancies (77.3%); pickup, delivery, dispatch and appointment coordination appeared in 78 (70.9%). The role is therefore distinct from physical driving, loading, picking or packing.
-
Records and performance data connect daily work to accountability. Operational documents and records appeared in 66 vacancies (60.0%), while KPI, status data and reporting appeared in 68 (61.8%). Frequently observed outputs included status and ETA updates, exception logs and recovery plans, shipment plans or dispatch boards, booking or transport orders, and shipping document sets.
-
A coherent course should own the post-release pickup-to-delivery control cycle. It should begin with an already authorized shipment and end with delivery evidence or a documented unresolved-exception handoff. It should not duplicate warehouse inventory and fulfilment, enterprise supply-chain strategy, procurement, driver training or regulated trade and transport instruction.
1. Research questions
The study addressed five questions:
- Which responsibilities recur in current public vacancies for logistics, transport, shipping, dispatch and delivery-operations coordinators?
- Which operating decisions are explicitly assigned to these roles?
- Which professional artifacts and records make the work reviewable?
- Which work situations create the greatest need for coordination?
- What curriculum content and boundaries follow directly from the observed work?
2. Reproducible method
2.1 Design
The study is a point-in-time purposive role-family analysis. Its unit of analysis is one paid public vacancy for one employer, role and location or requisition. The occupational boundary is coordination of physical shipments, freight, parcels, products, equipment or materials from release and pickup through delivery and operational closure.
Search-result counts were used only to locate individual vacancies. They were not treated as evidence of market size. The final analytical denominator is the 110 records that remained in the accepted corpus.
2.2 Search frame
Discovery used role-title families including logistics coordinator, logistics operations coordinator, transport coordinator, transportation coordinator, shipping coordinator, freight coordinator, dispatch coordinator, delivery operations coordinator, last-mile coordinator and adjacent operations titles containing explicit physical-shipment duties.
Searches combined titles with duty anchors such as shipment, freight, carrier, dispatch, route, pickup, delivery, POD, ETA, track-and-trace, TMS, 3PL, delivery window, appointment, delay, exception and escalation. Discovery covered employer career sites and employer-authorized systems including SmartRecruiters, Greenhouse, Workday, Paylocity, Ashby, Jobvite, Lever and iCIMS, plus individual public marketplace pages used in the accepted corpus.
2.3 Inclusion boundary
A vacancy was suitable when the public evidence showed physical-goods coordination rather than administrative work alone. The role needed observable pickup, dispatch, transport or delivery execution; a visibility or exception-control element; coordination across multiple parties; and enough source content to identify at least one decision and one work product.
Drivers, couriers, pickers, packers, loaders and warehouse associates were outside the role boundary when physical handling predominated. Inventory-only, purchasing-only, demand-planning-only, software-delivery, project-delivery and customer-service roles were excluded unless physical shipment coordination was central. Strategy-only management roles and roles dominated by regulated legal judgement were also outside scope.
2.4 Current status and deduplication
Each accepted record contains an individual source URL, employer or accountable publisher, role title, location, retrieval date, current-status evidence, evidence channel and limitation note. The accepted ledger was validated on 28 August 2026.
Deduplication used unique source URLs and employer-role-location or requisition identities. Deterministic validation found:
- 110 accepted records;
- 110 unique URLs;
- 110 unique deduplication keys;
- zero duplicate URL groups;
- zero duplicate deduplication-key groups;
- zero missing core fields.
2.5 Rights-safe evidence storage
The evidence ledger retains bibliographic facts, derived codes, one necessary 8–20-word excerpt per vacancy, current-status evidence and limitations. It does not retain full vacancy bodies, screenshots, logos, application questions, recruiter contact details or personal data. Findings in this report are aggregate paraphrases.
2.6 Coding and interpretation
The coding framework covered responsibilities, tools, decisions, professional artifacts and work situations. A signal was counted only when supported by the retained public evidence. Multiple signals could occur in one vacancy, so counts do not sum to 110.
A missing signal means “not observed in the retained public text.” It does not mean the employer or worker never performs that activity. Percentages are descriptive shares of this accepted sample and cannot be projected to all vacancies or workers.
3. Sample description
3.1 Source families and employers
The sample contains 78 employer-authorized ATS vacancies (70.9%) and 32 individual public marketplace vacancies (29.1%). It represents 101 unique employers. No duplicate URL or deduplication-key group remained in the accepted ledger.
3.2 Platform distribution
| Platform | Vacancies | Share of sample |
|---|---|---|
| SmartRecruiters | 26 | 23.6% |
| Indeed | 18 | 16.4% |
| LinkedIn Jobs | 14 | 12.7% |
| Greenhouse | 11 | 10.0% |
| Workday | 11 | 10.0% |
| Paylocity | 10 | 9.1% |
| Ashby | 7 | 6.4% |
| Jobvite | 6 | 5.5% |
| Lever | 6 | 5.5% |
| iCIMS | 1 | 0.9% |
| Total | 110 | 100.0% |
No single platform supplied more than 23.6% of the sample.
3.3 Geography
The corpus covers 15 countries. The United States supplied 64 records (58.2%), the United Kingdom 21 (19.1%), Australia 6 (5.5%), Canada 5 (4.5%), Egypt 3 (2.7%) and the Netherlands 2 (1.8%). Ethiopia, France, India, Malaysia, Mexico, Morocco, South Korea, Sweden and Vietnam each supplied one record.
This geographic distribution provides cross-border variety but is strongly weighted toward the United States and United Kingdom. It supports role-content analysis, not geographic prevalence claims.
3.4 Titles
The most common exact titles were Logistics Coordinator, 34 records (30.9%); Transport Coordinator, 17 (15.5%); Transportation Coordinator, 7 (6.4%); and Shipping Coordinator, 5 (4.5%). The remaining 47 records used variants such as logistics operations coordinator, transportation operations coordinator, outbound or international freight coordinator, last-mile coordinator, load planner/logistics coordinator and customer logistics coordinator.
The title variation reinforces the need to define the role by its work cycle rather than by one job title.
4. Findings
4.1 Primary responsibility signals
| Observed signal | Vacancies | Share of accepted sample |
|---|---|---|
| Stakeholder and customer communication | 105 | 95.5% |
| Milestone, ETA and delivery visibility | 103 | 93.6% |
| Delay and service-exception recovery | 94 | 85.5% |
| Carrier, driver and delivery-partner coordination | 85 | 77.3% |
| Pickup, delivery, dispatch and appointment coordination | 78 | 70.9% |
| KPI, status data and reporting | 68 | 61.8% |
| Operational documents and records | 66 | 60.0% |
These counts are non-exclusive.
4.2 Communication is operational control
Communication was the most frequently observed signal. The pattern was not generic “good communication.” Vacancy evidence tied communication to concrete operating purposes: confirming pickup or delivery windows, requesting carrier or driver status, warning customers about delay risk, aligning warehouses and 3PLs, escalating unresolved issues, and preserving handover information.
This implies that communication quality should be assessed through accuracy, timing, audience, evidence and next-action clarity. A polished message that contains an unsupported ETA is weaker than a concise update that distinguishes confirmed facts, assumptions, risks and required decisions.
4.3 Visibility is a continuous responsibility
Tracking and delivery visibility appeared in 103 vacancies. Employers described tracking milestones, checking ETAs, updating transport or order systems, monitoring driver or carrier status, confirming delivery and identifying at-risk shipments.
The recurring job is not merely to “look up tracking.” It is to maintain a usable control picture. That picture connects planned milestones, current evidence, exceptions, owners, next checks and communication commitments. A course should therefore teach status discipline: time-stamped updates, source attribution, controlled status labels, next-action ownership and closure criteria.
4.4 Exception recovery defines the role under pressure
Exception recovery appeared in 94 vacancies. Delay, missed pickup, failed delivery, weather, breakdown, damage, missing information, capacity shortfall and document discrepancies were common contexts. The principal explicit decision signal—recover, reroute, reschedule, hold or escalate—appeared in 40 records.
The result supports a structured exception method:
- establish the confirmed event and operational impact;
- protect safety and authority boundaries;
- classify urgency and service risk;
- identify permitted recovery options;
- assign an owner and next check;
- communicate facts and revised expectations;
- preserve the decision and evidence;
- close or hand off the issue.
This is a bounded operational method. It does not authorize a learner to make legal, safety, customs, insurance or commercial decisions outside their role.
4.5 Coordination operates through networks of parties
Carrier, driver and delivery-partner coordination appeared in 85 vacancies, while pickup, delivery, dispatch and appointment coordination appeared in 78. Many records also connected the coordinator with warehouses, 3PLs, suppliers, customer-service teams, sales, production or customer contacts.
The coordinator’s value lies in synchronizing commitments across parties that hold different pieces of the operating picture. This requires careful handoffs, confirmed responsibility, explicit due times and escalation routes. It also explains why a coordinator course should not be designed as a simplified warehouse course: the principal object is the cross-party delivery flow after release, not stock control or physical fulfilment.
4.6 Documents and data make execution reviewable
Operational documents and records appeared in 66 vacancies. KPI, status data and reporting appeared in 68. The record types varied by context, but the shared function was stable: create traceability for what was planned, what occurred, what changed, who was informed and whether delivery was closed.
The most frequently observed professional artifacts were:
| Artifact | Vacancies | Share of accepted sample |
|---|---|---|
| Status and ETA update | 38 | 34.5% |
| Exception log and recovery plan | 35 | 31.8% |
| Shipment plan or dispatch board | 25 | 22.7% |
| Booking or transport order | 21 | 19.1% |
| Shipping document set | 21 | 19.1% |
Artifact counts reflect explicit named or directly observable outputs in retained public text. Vacancy descriptions often omit routine work products, so these are minimum observed counts.
4.7 Dominant work situations
| Work situation | Vacancies | Share of accepted sample |
|---|---|---|
| Delay, disruption or service failure | 39 | 35.5% |
| Cross-functional and multi-party operations | 39 | 35.5% |
| High-volume, time-pressured operations | 27 | 24.5% |
The same vacancy could include more than one situation. These situations support scenario-based learning because they require learners to prioritize incomplete information, coordinate several actors and preserve an auditable record under time pressure.
5. Curriculum implications
5.1 Observable professional outcome
A defensible course outcome is:
Given an authorized shipment release, approved service arrangements, verified delivery constraints and changing operational events, produce and operate a reviewable Delivery Coordination Control Plan that connects pickup and delivery scheduling, milestone visibility, exception recovery, stakeholder updates, proof-of-delivery reconciliation and operational closure.
5.2 Recommended learning sequence
The evidence supports four connected learning blocks.
Block 1: Establish the control picture
Learners should interpret the shipment-release handoff, identify delivery constraints, confirm roles and escalation paths, prepare a booking request, coordinate appointments and build a shipment plan or dispatch board. The work begins after an upstream owner has released the shipment.
Block 2: Run live pickup-to-delivery control
Learners should update milestones, record evidence sources, maintain ETAs, identify at-risk movements, prioritize checks and coordinate drivers, carriers, delivery partners, 3PLs and internal teams.
Block 3: Recover exceptions and communicate decisions
Learners should triage delays and service failures, compare permitted recovery options, record the chosen next action, draft accurate updates, manage customer expectations and hand off issues that exceed their authority.
Block 4: Reconcile evidence and improve the operating cycle
Learners should check delivery confirmation and proof-of-delivery evidence, close or hand off open issues, reconcile the status record, review service indicators and propose a bounded corrective action.
5.3 Practical artifacts
A course aligned to the evidence should include original, vendor-neutral templates and realistic completed examples for at least these outputs:
- shipment-release coordination brief;
- pickup and delivery constraint register;
- carrier booking request;
- pickup and delivery appointment plan;
- shipment plan or dispatch board;
- milestone and ETA tracker;
- at-risk shipment watchlist;
- stakeholder update record;
- consignee communication log;
- exception triage record;
- recovery option comparison;
- failed-delivery case record;
- escalation and handover note;
- proof-of-delivery check;
- delivery closure record;
- claims-evidence handoff;
- daily delivery control board;
- KPI and service review;
- data-quality reconciliation;
- corrective-action record.
These artifacts should use fictional data and tool-neutral fields. They should not reproduce employer forms, carrier portals or proprietary system screens.
5.4 AI practice
AI-assisted work should remain bounded and reviewable. Suitable uses include checking a fictional record for missing fields, classifying supplied exception notes, comparing approved recovery options, drafting a status update from confirmed facts and identifying inconsistencies between a delivery record and proof evidence.
A human remains responsible for shipment release, operational commitments, carrier or driver allocation, route constraints, compliance, customer promises, claims, exception closure and production-system changes. Learners should never enter real customer addresses, live tracking data, driver information, rates, contracts or credentials into an unapproved AI tool.
5.5 Portfolio and regulatory boundaries
The course should not teach:
- receiving, storage, stock control, counting, picking, packing or warehouse equipment;
- enterprise network design, facility strategy or supply-chain architecture;
- carrier sourcing, tendering, contract negotiation or invoice approval;
- vehicle operation, driver technique, vehicle maintenance or load securement;
- live driver-hours, tachograph, licensing or route-legality decisions;
- dangerous-goods classification, packing, declarations or labels;
- tariff classification, customs valuation, origin, sanctions, licences or customs filing;
- pharmaceutical GDP, cold-chain qualification or other controlled distribution procedures;
- legal liability, insurance coverage or compensation decisions.
These boundaries preserve a distinct pickup-to-delivery coordination outcome and avoid converting general education into regulated or jurisdiction-specific professional advice.
6. Practical application
6.1 Suggested applied case
A suitable case begins with twelve already released shipments assigned to approved services. The learner receives verified delivery windows, customer priorities, carrier contacts, milestone data and escalation rules. During the operating day, several events occur: a pickup misses its slot, one ETA becomes unreliable, a consignee requests a new window, a driver reports an access problem, and one completed delivery lacks usable proof evidence.
The learner’s principal task is to operate one Delivery Coordination Control Plan. The final deliverable should show:
- a current control picture for all twelve shipments;
- prioritized actions and owners;
- evidence-based ETAs and updates;
- documented exception choices within stated authority;
- clear escalation for issues outside authority;
- proof-of-delivery reconciliation;
- operational closure or a complete unresolved-issue handoff;
- a short service review identifying one bounded improvement.
The assessment should reward traceability, prioritization, communication accuracy, authority awareness and closure discipline. It should not reward invented facts or confident guesses.
6.2 Workplace use
A graduate should be able to enter a coordinator role with a repeatable operating routine:
- start from the authorized handoff;
- confirm what must move, when and under which constraints;
- keep the live record accurate;
- expose risk before a service failure becomes harder to recover;
- coordinate the next action with the responsible party;
- communicate only confirmed information and clearly labelled estimates;
- preserve delivery and exception evidence;
- close the record or hand it off without information loss.
This outcome is useful across freight forwarding, manufacturing distribution, retail and e-commerce delivery, industrial equipment movement, service-parts logistics and other product-moving organizations. Employer-specific systems and local rules still require workplace training.
7. Limitations
- Purposive design. The sample is not random and does not estimate the number or share of jobs in any market.
- Geographic concentration. The United States and United Kingdom contribute 85 of 110 records (77.3%). Findings should not be presented as balanced global prevalence.
- Public and English-language bias. Roles advertised only in local languages, closed networks or poorly indexed systems are underrepresented.
- Source mix. Seventy-eight records came from employer-authorized ATS pages and 32 from individual public marketplace pages. Marketplace pages can change, close or reproduce employer text incompletely.
- Point-in-time status. Vacancies can close or change after 28 August 2026. The inventory records the evidence available for this study date.
- Vacancy-text limits. Job descriptions can be incomplete, aspirational or reused. They describe requested work, not verified day-to-day practice or effectiveness.
- Coding limits. A signal not observed in retained text may still exist in the job. Artifact and decision counts are especially sensitive to brief vacancy descriptions.
- Title variation. Similar work appears under many titles, while identical titles can cover different work. The study therefore uses duty-based inclusion.
- Sector and legal variation. Customs, safety, labour, dangerous-goods, privacy and controlled-distribution rules vary by jurisdiction and sector. Their appearance in vacancies does not support generic procedural instruction.
- No outcome claim. The evidence does not prove that a course will cause employment, promotion, salary growth, productivity, cost savings, compliance or service improvement.
8. Rights basis
The study uses public vacancy pages as factual evidence about role titles, locations and requested work. The research record stores only the minimum material needed for auditability: source facts, derived codes, one short 8–20-word excerpt per vacancy, current-status evidence and limitations.
Full vacancy bodies, logos, screenshots, application forms, recruiter contact details and personal information are not reproduced. Aggregate findings are newly written paraphrases. Employer and platform names identify evidence sources and do not imply endorsement, affiliation or approval.
Course materials derived from this research should use original MTF taxonomies, fictional organizations, synthetic shipment data and newly written templates. They should not copy job descriptions, carrier terms, rate cards, tracking interfaces, third-party templates, standards text or another course’s expression.
Named standards and rule systems require additional care. Incoterms® is an ICC trademark and its Rules are protected; ISO publications are protected; dangerous-goods and customs requirements are controlled by authoritative sector and jurisdiction sources. The course should use recognition-and-escalation treatment instead of reproducing or replacing protected or regulated material.
9. Conclusion
The accepted sample shows a coherent occupational pattern. Logistics and delivery coordinators keep a multi-party pickup-to-delivery flow visible, synchronized and reviewable. Their work combines booking and appointment coordination, live milestone control, exception recovery, evidence-based communication, document discipline and performance review.
The strongest learning need is not a broad survey of supply-chain theory. It is an operating method for turning an authorized shipment release into controlled delivery progress, accurate updates, recoverable exceptions and documented closure. A course built around that method can be practical, text-based and transferable across sectors while remaining distinct from warehouse execution, procurement, driving and regulated trade or transport practice.
References
- MTF Institute. Accepted vacancy corpus: Logistics Coordination and Delivery Operations. Point-in-time ledger of 110 individual public vacancies, retrieved 28 August 2026. Full source inventory appears in Appendix B.
- MTF Institute. Vacancy Sampling and Coding Method, version 1.0, 28 August 2026.
- MTF Institute. Vacancy Corpus Validation, 28 August 2026: 110 accepted rows, 110 unique URLs, 110 unique deduplication keys and zero missing core fields.
- MTF Institute. Vacancy Coding Summary, 28 August 2026.
- U.S. Bureau of Labor Statistics. Logisticians, Occupational Outlook Handbook. Updated 27 August 2026. This broader occupation is contextual evidence, not the study sample.
- O*NET OnLine. Cargo and Freight Agents, 43-5011.00. Updated 2026. “Logistics Coordinator” appears among reported titles; the taxonomy is contextual evidence.
- International Chamber of Commerce. Incoterms® Rules trademark and copyright policy.
- International Organization for Standardization. ISO copyright policy.
- United Nations Economic Commission for Europe. ADR 2025.
- International Civil Aviation Organization. Technical Instructions for the Safe Transport of Dangerous Goods by Air.
- European Commission. Customs declaration.
- European Commission. Driving and rest times.
- European Medicines Agency. Good distribution practice.
Appendix A. Coding inventory used in the report
Primary responsibility signals
- Communication: operational customer and stakeholder updates.
- Tracking: milestones, location, ETA, status, delivery confirmation or proof evidence.
- Booking: carrier booking, dispatch, pickup or delivery scheduling and appointments.
- Exception: delay, missed window, damage, loss, data error or service-failure recovery.
- Carrier: coordination with carriers, drivers, brokers, forwarders or delivery partners.
- Documents: creation, checking, distribution or retention of shipping and operational records.
- KPI: status data, reports, service indicators or performance analysis.
Principal decision signal
- Exception action: recover, reroute, reschedule, hold or escalate within stated authority.
Principal artifact signals
- status and ETA update;
- exception log and recovery plan;
- shipment plan or dispatch board;
- booking or transport order;
- shipping document set.
Principal work-situation signals
- delay, disruption or service failure;
- cross-functional and multi-party operations;
- high-volume, time-pressured operations.
Appendix B. Accepted vacancy source inventory
All records were retrieved on 28 August 2026. URLs are provided for reproducibility; future availability is not assured.
| ID | Employer | Role | Location | Platform | Individual vacancy URL |
|---|---|---|---|---|---|
| LCDO-A-001 | Fluidstack | Transportation Coordinator | Remote, United States | Ashby | Source |
| LCDO-A-002 | Cargomatic | Operations Coordinator | Bloomington, California, United States | Greenhouse | Source |
| LCDO-A-003 | Expeditors | Logistics Coordinator - Transcon | United States, location not exposed | SmartRecruiters | Source |
| LCDO-A-004 | Winsupply | Logistics Coordinator | Jacksonville, Florida, United States | SmartRecruiters | Source |
| LCDO-A-005 | Louis Dreyfus Company | Logistics Coordinator | Upper Sandusky, Ohio, United States | SmartRecruiters | Source |
| LCDO-A-006 | Woongjin | Logistics Coordinator - Bilingual Korean/English | Cerritos, California, United States | SmartRecruiters | Source |
| LCDO-A-007 | Arista Networks | Logistics Coordinator (APAC Service Operations) | Malaysia | SmartRecruiters | Source |
| LCDO-A-008 | Figure | Deployment Logistics Lead | San Jose, California, United States | Greenhouse | Source |
| LCDO-A-009 | British Homes Direct | Transport Coordinator - Delivery Routing & Planning | Rochdale, England, United Kingdom | Indeed | Source |
| LCDO-A-010 | Roseview Windows | Transport Coordinator | Olney, England, United Kingdom | Indeed | Source |
| LCDO-A-011 | KG Talent / Metroll | Transport Coordinator | Pakenham, Victoria, Australia | Indeed | Source |
| LCDO-A-012 | Sunbelt Rentals | Transport Coordinator | Chessington, England, United Kingdom | Indeed | Source |
| LCDO-A-013 | OnTrac | Logistics Coordinator | Remote, United States | LinkedIn Jobs | Source |
| LCDO-A-014 | Packaging Co | Logistics Coordinator | Los Angeles, California, United States | LinkedIn Jobs | Source |
| LCDO-A-015 | Swift Transportation | Logistics Transportation Coordinator | Phoenix, Arizona, United States | LinkedIn Jobs | Source |
| LCDO-A-016 | Sigma | Transportation Coordinator | Denton, Texas, United States | LinkedIn Jobs | Source |
| LCDO-A-017 | Medline | Transportation Coordinator | Northbrook, Illinois, United States | LinkedIn Jobs | Source |
| LCDO-A-018 | Intermountain Health | Transportation Coordinator | South Jordan, Utah, United States | LinkedIn Jobs | Source |
| LCDO-A-019 | Integrity Express Logistics | Logistics Coordinator | Denver, Colorado, United States | LinkedIn Jobs | Source |
| LCDO-A-020 | Next | Transport Coordinator | Pontefract, England, United Kingdom | LinkedIn Jobs | Source |
| LCDO-A-021 | Zenith Express | Logistics Coordinator | Green Bay, Wisconsin, United States | Indeed | Source |
| LCDO-A-022 | Williams-Sonoma Supply Chain | Logistics Coordinator | Memphis, Tennessee, United States | LinkedIn Jobs | Source |
| LCDO-A-023 | Skyline Courier and Logistics | Logistics Coordinator | Atlanta, Georgia, United States | Indeed | Source |
| LCDO-A-024 | Epiroc | Logistics Coordinator | Akron, Ohio, United States | Indeed | Source |
| LCDO-A-025 | EVE International Logistics | Logistics Coordinator | Chicago, Illinois, United States | Indeed | Source |
| LCDO-A-026 | Aston Carter client | Logistics Coordinator | Salt Lake City, Utah, United States | LinkedIn Jobs | Source |
| LCDO-A-027 | Expeditors | Transportation Operations Coordinator | Addison, Texas, United States | LinkedIn Jobs | Source |
| LCDO-A-028 | DHL Supply Chain | Logistics Operations Coordinator | Livonia, Michigan, United States | LinkedIn Jobs | Source |
| LCDO-A-029 | AGS Logistics | Last Mile Operations Coordinator | South San Francisco, California, United States | LinkedIn Jobs | Source |
| LCDO-A-030 | Bunge | Logistics Coordinator | Russell, Manitoba, Canada | Indeed | Source |
| LCDO-A-031 | Kelling Group | Logistics Coordinator | Normanton, England, United Kingdom | Indeed | Source |
| LCDO-A-032 | Gateway | Transport Coordinator | Kingston upon Hull, England, United Kingdom | Indeed | Source |
| LCDO-A-033 | Circulus CRM | Transport Coordinator | Glasgow, Scotland, United Kingdom | Indeed | Source |
| LCDO-A-034 | Tezlom Logistics client | Transport Operations Coordinator | Warrington, England, United Kingdom | Indeed | Source |
| LCDO-A-035 | Great Bear / Culina Group | Transport Coordinator | Minworth, England, United Kingdom | Indeed | Source |
| LCDO-A-036 | Gist / M&S | Transport Coordinator | Nuneaton, England, United Kingdom | Indeed | Source |
| LCDO-A-037 | Wayfair | Transport Coordinator | Lutterworth, England, United Kingdom | Indeed | Source |
| LCDO-A-038 | Linde / BOC Australia | Logistics Coordinator | North Ryde, New South Wales, Australia | Indeed | Source |
| LCDO-A-039 | Work With Island | International Logistics Coordinator | Paris, France | LinkedIn Jobs | Source |
| LCDO-A-040 | Skirting 4 U | Transport Coordinator | Walsall, England, United Kingdom | Indeed | Source |
| LCDO-B-001 | Sotheby's | Shipping Coordinator | New York, New York, United States | Greenhouse | Source |
| LCDO-B-002 | Pon.Bike | Shipping Coordinator | Rincon, Georgia, United States | Greenhouse | Source |
| LCDO-B-003 | FuseGlobal | Transportation Coordinator | Remote, United States | Greenhouse | Source |
| LCDO-B-004 | Four Hands | Logistics Coordinator, Outbound | Austin, Texas, United States | Greenhouse | Source |
| LCDO-B-005 | Xometry | Logistics Coordinator, International Freight | Gaithersburg, Maryland, United States | Greenhouse | Source |
| LCDO-B-006 | SMA America | Forward Logistics Coordinator | Remote, United States | Greenhouse | Source |
| LCDO-B-007 | YQN | Logistics Operation Coordinator | Fontana, California, United States | Greenhouse | Source |
| LCDO-B-008 | Doka USA | Logistics Coordinator | Lehi, Utah, United States | SmartRecruiters | Source |
| LCDO-B-009 | Progressive Technology Solutions | HP PageWide Web Press Logistics Coordinator | Corvallis, Oregon, United States | SmartRecruiters | Source |
| LCDO-B-010 | Manitoulin Group of Companies | Logistics Coordinator | Canada | SmartRecruiters | Source |
| LCDO-B-011 | TOMRA | Customer Logistics Coordinator | Rotterdam, New York, United States | SmartRecruiters | Source |
| LCDO-B-012 | Sika | Logistics Coordinator | Lewisville, Texas, United States | SmartRecruiters | Source |
| LCDO-B-013 | Louis Dreyfus Company | Logistics Coordinator | Addis Ababa, Ethiopia | SmartRecruiters | Source |
| LCDO-B-014 | Mondiale VGL | Airport Transport Coordinator | Australia | SmartRecruiters | Source |
| LCDO-B-015 | Progress Rail | Transport Coordinator | Nottingham, England, United Kingdom | SmartRecruiters | Source |
| LCDO-B-016 | Culina Group | Transport Coordinator | Sheffield, England, United Kingdom | SmartRecruiters | Source |
| LCDO-B-017 | Culina Group | Transport Coordinator | Bolton, England, United Kingdom | SmartRecruiters | Source |
| LCDO-B-018 | Mitsubishi Power EMEA | Shipping Coordinator | United Kingdom | SmartRecruiters | Source |
| LCDO-B-019 | Spreetail | Senior Logistics Coordinator | Remote, Nebraska, United States | Lever | Source |
| LCDO-B-020 | Zeeco | Logistics Coordinator | Broken Arrow, Oklahoma, United States | Lever | Source |
| LCDO-B-021 | AIP Connect | Operations Logistics Coordinator | Mississauga, Ontario, Canada | Lever | Source |
| LCDO-B-022 | Maersk | 4PL Customer Service Agent - Booking Management | Ho Chi Minh City, Vietnam | Workday | Source |
| LCDO-B-023 | Sharpsmart | Transport Coordinator, Nightshift | Rainham, England, United Kingdom | Lever | Source |
| LCDO-B-024 | Bosta | Last Mile Hub Senior Coordinator | Cairo, Egypt | Lever | Source |
| LCDO-B-025 | Bosta | Last Mile Hub Coordinator | Mansoura, Egypt | Lever | Source |
| LCDO-B-026 | T1 Energy | Logistics Coordinator | Dallas, Texas, United States | Ashby | Source |
| LCDO-B-027 | Harmattan AI | Logistics Coordinator | Morocco | Ashby | Source |
| LCDO-B-028 | Picogrid | Operations and Logistics Coordinator | El Segundo, California, United States | Ashby | Source |
| LCDO-B-029 | Pergolux | Logistics Coordinator | United States | Ashby | Source |
| LCDO-B-030 | FuriosaAI | Operations - Logistics | Seoul, South Korea | Ashby | Source |
| LCDO-B-031 | Air Liquide | Stock and Transport Coordinator | Vasteras, Sweden | Workday | Source |
| LCDO-B-032 | Samsung SDS | Transport Coordinator | Maasvlakte, Netherlands | Workday | Source |
| LCDO-B-033 | Marken, a UPS company | Transport Coordinator | Miami, Florida, United States | Workday | Source |
| LCDO-B-034 | MillerKnoll | Transport Co-ordinator | Melksham, England, United Kingdom | Workday | Source |
| LCDO-B-035 | Live Nation Entertainment | Shipping Coordinator | New York, New York, United States | Workday | Source |
| LCDO-B-036 | IFF | Logistics Coordinator I | Cairo, Egypt | Workday | Source |
| LCDO-B-037 | Arbex | Logistics Coordinator | Melbourne, Victoria, Australia | Workday | Source |
| LCDO-B-038 | Maersk | 4PL Export Logistics Coordinator | Sydney, New South Wales, Australia | Workday | Source |
| LCDO-B-039 | Bega Group | Distribution and Logistics Coordinator - Export | Tatura and Docklands, Victoria, Australia | Workday | Source |
| LCDO-B-040 | Jabil | Logistic Coordinator | Ranjangaon, India | Workday | Source |
| VAC-C-001 | Expeditors | Logistics Coordinator (Network Management Center) | Ciudad Apodaca, Nuevo Leon, Mexico | SmartRecruiters | Source |
| VAC-C-002 | Arvato | Transport Coordinator | Echt, Netherlands | SmartRecruiters | Source |
| VAC-C-003 | Arvato | Service Delivery Coordinator | Corby, Northamptonshire, United Kingdom | SmartRecruiters | Source |
| VAC-C-004 | Ingram Content Group | Shipping Coordinator - 2nd Shift | La Vergne, Tennessee, United States | SmartRecruiters | Source |
| VAC-C-005 | Pact Group | Facility & Logistics Coordinator | Carson, California, United States | SmartRecruiters | Source |
| VAC-C-006 | REXEL | Transport Coordinator | Aston Clinton, Aylesbury, United Kingdom | SmartRecruiters | Source |
| VAC-C-007 | SBT Global, Inc. | Logistics Coordinator | Miami, Florida, United States | SmartRecruiters | Source |
| VAC-C-008 | Sika AG | Customer Service and Logistics Coordinator | Oakville, Ontario, Canada | SmartRecruiters | Source |
| VAC-C-009 | Woongjin, Inc. | Logistics Coordinator (AIR & Ocean Operations) | Santa Ana, California, United States | SmartRecruiters | Source |
| VAC-C-010 | Sika AG | Logistics Coordinator | Marion, Ohio, United States | SmartRecruiters | Source |
| VAC-C-011 | Carvana | Transportation Coordinator | Tempe, Arizona, United States | Greenhouse | Source |
| VAC-C-012 | Four Hands | Logistics Coordinator, Inbound | Austin, Texas, United States | Greenhouse | Source |
| VAC-C-013 | SIO Logistics | Logistics Coordinator | San Antonio, Texas, United States | Ashby | Source |
| VAC-C-014 | Funko | Logistics Coordinator, UK | Coventry, England, United Kingdom | Jobvite | Source |
| VAC-C-015 | A. M. Castle & Co. | Transportation Coordinator | Warsaw, Indiana, United States | Jobvite | Source |
| VAC-C-016 | Blount Fine Foods | Corp Transportation Coordinator | Fall River, Massachusetts, United States | Jobvite | Source |
| VAC-C-017 | Premier Trailer Leasing | Loss Damage Waiver / Transportation Coordinator | Plano, Texas, United States | Jobvite | Source |
| VAC-C-018 | ASUS USA | Logistics Coordinator | Fremont, California, United States | Jobvite | Source |
| VAC-C-019 | Lordco Auto Parts | Logistics Coordinator | Port Coquitlam, British Columbia, Canada | Jobvite | Source |
| VAC-C-020 | Sazerac | Shipping Coordinator | Bardstown, Kentucky, United States | iCIMS | Source |
| VAC-C-021 | Euro Foods Inc DBA Citterio USA | Load Planner/Logistics Coordinator | Freeland, Pennsylvania, United States | Paylocity | Source |
| VAC-C-022 | Bender, Inc. | Logistics Coordinator | Exton, Pennsylvania, United States | Paylocity | Source |
| VAC-C-023 | Container Centralen Inc. | Logistics Coordinator | Winter Garden, Florida, United States | Paylocity | Source |
| VAC-C-024 | Perpetua Resources Idaho, Inc. | Logistics Coordinator | Donnelly, Idaho, United States | Paylocity | Source |
| VAC-C-025 | Pero Family Farms | Transportation Coordinator, MI | Benton Harbor, Michigan, United States | Paylocity | Source |
| VAC-C-026 | Ark Transportation Ltd | Logistics Coordinator - Domestic | United States, location not exposed | Paylocity | Source |
| VAC-C-027 | Alsum Farms & Produce | Logistics Coordinator | Friesland, Wisconsin, United States | Paylocity | Source |
| VAC-C-028 | Greenwood Associates, Inc. | Logistics Coordinator | Niles, Illinois, United States | Paylocity | Source |
| VAC-C-029 | NRTC Alabama, Inc. | Customer Service and Logistics Coordinator | Detroit, Michigan, United States | Paylocity | Source |
| VAC-C-030 | IMDEX | Logistics Coordinator | Elko, Nevada, United States | Paylocity | Source |
Continue learning
The capabilities examined in this report are developed in MTF Institute's Professional Certificate in Logistics Coordination and Delivery Operations through structured learning and applied practice.