Single point of control
- The full parcel lifecycle, from registration to delivery, in one interface
- Custom shipping solutions keep carrier selection flexible and invisible to the shipper
- A complete audit trail of every action: who, when, which parcel
One platform runs the whole lifecycle of a parcel: rule-based carrier routing, labels in 0.5 seconds natively and in 2–5 seconds when a carrier's API is in the loop, hub consolidation, normalised tracking and managed billing. Operators configure the rules once; V-TER Ship applies them to every shipment automatically.
From registration to delivery, each parcel moves through a strictly controlled sequence. Nothing depends on a manual decision per shipment.
Created in the UI, through the REST API, from a CSV/XLSX file in a standard or custom format with column-to-attribute mapping, by SFTP batch, or imported straight from a marketplace. Outbound and return parcels alike, including returns linked to an outbound parcel already in the system.
Prioritised routing rules check weight, dimensions, destination country, ZIP range, parcel category, description keywords, incoterm, shipper and shipping solution, and select the carrier and service. Least Cost Routing can decide between eligible options.
A native label renders in 0.5 seconds through the API, the UI or a batch. A carrier-issued label takes 2–5 seconds, the difference being the carrier's API response time. Where the carrier label is not yet available, an internal system label lets physical processing start immediately.
The hub operator scans the parcel and sees all of its data; the status moves to Accepted. Parcels are consolidated into Parcel Groups; closing a group signals readiness for carrier handover, with optional carrier-side manifesting. Shippers can also create groups for consolidations handled outside system hubs.
Statuses arrive from carriers in any format over SFTP, API or webhooks and are normalised into a unified set of system events. End recipients get e-mail notifications configurable by status, shipper, country, carrier and other parcel attributes.
For DDU shipments the T&D module uses HSCodifi to determine the HS code from item descriptions or images, calculates duties and taxes, and holds the parcel at the hub until the recipient pays through a payment gateway. Rate cards apply to every operation automatically; the Invoice Planner issues invoices on schedule.
Routing, billing and validation logic are configured, not coded. Everything else a first- or last-mile operator needs is already in the platform.
Plug into the stack you already run.
Full programmatic access: parcel creation, tracking, management and label retrieval.
Batch data exchange: parcel import, tracking event export, carrier invoice upload.
Direct order ingestion from e-commerce platforms, each order becoming a parcel ready to route.
Native connectivity to ACP and equivalent systems for electronic pre-declaration and automated clearance.
The logic that removes manual decisions.
Prioritised rules over weight, dimensions, country, ZIP, category, keywords, incoterm and more.
Several credential sets per carrier under different shippers, hubs or shipping solutions.
Return addresses assigned automatically by shipper, hub, carrier or destination country.
Field-level checks by shipper, hub, carrier and other parameters, applied at creation.
What the hub and the support desk work in every day.
An internal label lets the hub process a parcel before the carrier label exists.
Consolidation at the hub or outside it, with optional carrier-side manifesting on close.
Recipient addresses stored for reuse, with CSV/XLSX import and export.
General parcel report, acceptance report, undeliverables report.
Granular roles for the operator, from Super Admin to Hub Worker, and for shippers.
Every stage controlled, transparent and billable.
AI HS code prediction, duty and tax calculation, parcel held until paid, full transaction audit trail.
Versioned rate cards in several formats, surcharges, Invoice Planner, carrier invoice reconciliation.
Who did what to which parcel, and every API request with method, code, URI and timing.
V-TER Ship is API-first: what the UI does, the REST API does too. The public reference documents every endpoint with its request and response schemas, and it lives on the example environment, next to a running system.
Create, update, cancel and query parcels, one at a time or in batches.
Retrieve the carrier label or the native render in the formats the hub prints.
Read the normalised event set of any parcel, the same across every carrier.
Create parcels and request their labels in bulk through the batch endpoint, rather than one call per parcel.
Every stage of the operation becomes controlled, transparent and billable, with a depth of configurability off-the-shelf TMS products do not reach.
Every V-TER platform shares one data layer and one API, so connecting two of them is configuration, not an integration project. Here is what each one does for V-TER Ship.
Rate cards, surcharges and the Invoice Planner run inside V-TER Ship: every parcel event that should be billed becomes a transaction, with no spreadsheet in between.
Explore V-TER Ship Billing Carrier connectivity APIEvery carrier V-TER Ship routes to is reached through Last Mile Connect: one API for booking, labels and tracking across 200+ carriers, new ones added by configuration.
Visit Last Mile Connect (dedicated site) Customs compliance AIThe T&D module calls HSCodifi on every DDU parcel: HS code from the item description or image, duties and taxes calculated, and the parcel held at the hub until the recipient has paid.
Visit HSCodifi (dedicated site) Warehouse managementPack confirmation in Fulfillment WMS creates the parcel in V-TER Ship with weight and dimensions already captured, so label and carrier are settled before the box leaves the packing station.
Explore Fulfillment WMS Hub-to-hub network managementClosed Parcel Groups become bags and pallets in V-TER Linehaul, so the hub-to-hub leg, its customs gating and every departure scan stay on the same parcel record.
Explore V-TER Linehaul Reverse logisticsA return created in V-TER Returns is linked to the outbound parcel already in V-TER Ship, and its label is issued through the same carrier network.
Explore V-TER Returns White-label parcel forwardingEasyForward operators create and route their forwarding shipments through V-TER Ship: their rate cards, their carrier rules, the label printed in the warehouse.
Explore EasyForwardThe platform adapts to the operational model of each company, from the routing rule set to the branding of its public tracking pages.
Hubs and consolidators receiving parcels from online stores and handing them off to last-mile carriers.
Parcel flows from multiple shippers across several hubs, with separate billing per client.
Direct control over label generation and tracking for parcels created from customer orders.
DDU shipments that need duties and taxes calculated automatically and collected from the recipient.
Hours for a first connection. V-TER Ship connects to your existing marketplaces and carriers, and V-TER's team handles the carrier mapping; you validate the rules and the output. A standard onboarding then covers hub and shipper configuration, routing rules, carrier credentials, testing of booking, label, tracking and billing, and a phased go-live without interrupting current operations.
A native label, one V-TER Ship renders itself, takes 0.5 seconds per parcel through the API. A label issued by the carrier's own API takes 2–5 seconds: that wait is the carrier's response time, a third-party dependency V-TER Ship cannot shorten. For bulk runs the batch endpoint takes the parcels in one go instead of one call each, and the internal system label keeps the hub moving while carrier labels are still being issued.
V-TER Ship keeps a carrier fallback queue. If a primary carrier's API is unavailable, the system can re-route to a pre-configured fallback carrier or hold parcels in a pending queue with operator alerts. No parcel is silently dropped.
Yes. A return can be created as a standalone parcel or linked to an outbound parcel already in the system, with return addresses assigned automatically by rule. For a full reverse-logistics operation, with a consumer portal and hub inspection, V-TER Returns runs on the same data layer.
Whatever the operation needs on day one. T&D, the Invoice Planner and Geo Zones are activated as needed, and the platform runs standalone or alongside Last Mile Connect, Fulfillment WMS, HSCodifi and V-TER Returns without additional integration work.
Test V-TER Ship on 10–20 parcels and see the difference for yourself: routing without decisions, labels without waiting, and billing that closes itself.