Keep documents with the shipment
A planned shared context for document records and clearance information.
Explore your future workspaceRegistration and private access are in preparation. This public view contains no client records.
VIxIP Customs
Make every release decision traceable.
A planned coordination workspace for shipment documents, HOLD and CLEAR status, and the authorised decisions behind a release.
For teams coordinating shipment documents and release decisions
The goods are here. Is the release decision clear?
Customs is being designed around the documents, clearance status and authorised decisions behind a shipment, so a status change has a record people can follow.
01
Gather
Bring shipment document records together.
02
Review
Make HOLD and CLEAR status visible in context.
03
Decide
Keep authorised release decisions and their history traceable.
Illustrative workflow · planned product scope
Give a hold a visible place
HOLD and CLEAR visibility is central to the product direction.
Record who made the decision
Permission-led release and decision history are part of the planned scope.
The detail behind the product
Designed for the decisions
your team makes every day.
Our development direction, shaped by real operating requirements. Labels distinguish development foundations from planned end-to-end workflows; customer availability is confirmed separately.
Planned workflow
Evidence behind the status
Keep the relevant shipment documents and source communication available alongside the clearance decision.
Planned workflow
A message is not a release authority
A proposed instruction needs the right sender, shipment context and authorised review before it can become an operational decision.
Planned connected workflow
Separate clearance from warehouse actions
Keep customs clearance, unload permission, warehouse holds and dispatch release distinct, so one status does not imply every approval.
Planned workflow
A history people can follow
Record the decision, responsible person and relevant evidence. Customs-provider submissions and write-back are separate integration work.
Development status and availability
Customs is in development. This is coordination software in preparation, not a live customs-filing service or a guarantee of regulatory compliance.
Bring us your real workflow
How do warehouse and clearance teams confirm that the latest release decision is the one being acted on?
Discuss the process, the exceptions and what a useful pilot would need to demonstrate.
What Customs brings to your team
- Shipment document records
- HOLD and CLEAR visibility
- Controlled release decisions
- Auditable decision history
In development. Customs submissions and external provider write-back are not available.
Communication connected to the work
Keep the conversation.
Keep the operational context.
Our messaging work is designed to connect the office, warehouse floor and client around the relevant job. Arrival photos, seal details, instructions and completion updates should not lose their meaning as they pass between teams.
01 / Capture
Keep the source
Retain permitted communication and evidence with its origin and the relevant operational context.
02 / Review
Resolve uncertainty
Route unmatched or ambiguous instructions for human review. Check authority before a business decision.
03 / Follow through
Know the handover state
The planned delivery trail distinguishes queued, submitted, delivered and uncertain outcomes.
Work with existing channels
WeCom and WhatsApp Business integration work is underway. Supported account and channel options need verification; access to existing personal chats or groups is not assumed.
Human decisions stay human
The design links messages to review, rather than treating message text as automatic permission to unload, clear goods or dispatch.
Each client’s connection stays separate
Provider accounts, site mappings and access are designed to stay specific to the organisation they serve.
Planned internal communication
Direct and group conversations
Internal chat is being developed around organisation, site and role access, so conversations reach the relevant team.
Planned staff communication
Announcements and a staff feed
A shared place for targeted updates and team information is part of the messaging scope.
Planned support workflow
A question with an owner
Support tickets are planned with assignment, progress and resolution history, separating customer replies from private staff notes.
Planned assisted support
AI assistance with human handover
AI-assisted support is part of the development direction, with escalation to a person and no automatic operational approvals.
Integration in development. Connection verification is a technical milestone, not live message processing. End-to-end receipt, review and delivery acceptance remain pending. Messaging packaging and availability will be confirmed separately.