Clear answers before the work begins.
We prefer useful specifics to broad promises. Here are the questions teams most often bring to a first conversation.
How long does implementation take?
A focused pilot can often be scoped in several weeks, while a multi-source, multi-facility rollout may take several months. Timing depends on source readiness, access approvals, workflow scope, and how quickly operational owners can validate definitions. We agree on stages and decision gates before work begins.
What data sources can Meridian use?
Common sources include transportation and warehouse systems, ERP, telematics, EDI messages, carrier portals, appointment tools, spreadsheets, and documented APIs. We assess source quality and refresh patterns before committing to a view or workflow.
Do we need to replace our existing systems?
No. The work is designed to connect and clarify existing operational systems, not force a rip-and-replace. We map available interfaces and agree on the smallest reliable connection that supports the objective.
How do you approach security?
Access is scoped to the agreed engagement and operational need. We document data flows, roles, and retention expectations with the customer, use appropriate technical and organizational safeguards, and avoid requesting credentials or information that is not required. Specific controls are reviewed as part of discovery.
Can different teams have different user roles?
Yes. Views and workflows can be organized around the responsibilities of planners, dispatchers, facility leads, analysts, and executives. Access scope should reflect each organization’s policies and the information needed for a role.
What does onboarding include?
Onboarding includes stakeholder alignment, source and workflow mapping, definitions, data validation, focused pilot configuration, role-based walkthroughs, and a review cadence. We document owners and decisions so the capability can be sustained after launch.
Can we keep our existing reports?
Usually. Existing reports provide useful measures and history. We review them alongside the decisions people make, clarify conflicting definitions, and complement or consolidate reports where that helps rather than discarding useful work by default.
How does carrier visibility work?
Carrier updates from available EDI, portal exports, tracking feeds, or other agreed sources can be normalized into a common milestone and exception timeline. Actual visibility depends on the source coverage, update timing, and data-sharing permissions.
What warehouse analytics can you support?
Typical work includes appointment pressure, throughput, task flow, inventory movement, labor capacity, and shift-level operating review. We begin with the facility questions and data available rather than assuming every warehouse measures work the same way.
What support is available after launch?
Customer support is available Monday–Friday, 8:00 a.m.–6:00 p.m. Eastern Time, excluding U.S. federal holidays. Requests are prioritized as Urgent, High, Normal, or Guidance with initial response targets described on the Support page.
How are contracts structured?
Scope, fees, milestones, access responsibilities, and any continuing support are set out in a written agreement. Engagements may be scoped around discovery, a defined implementation, or ongoing support. Terms vary by scope and are confirmed before work starts.
Is Meridian suitable for midsize operations?
Yes. Midsize organizations often benefit from starting with one high-friction workflow, a constrained data scope, and a clear result measure. We shape the approach to team capacity and operational complexity rather than requiring enterprise-scale transformation.