Complete the workspace checklist, confirm your organisation details, then open the Operations Inbox or Permit Parser. Your navigation shows only the tools available to your organisation.
Help and recovery
Something stopped? Find the next safe step.
Start with the task you were trying to finish. You do not need to know the product name or read a wall of documentation.
Search by task, visible status or the problem in front of you.
12 matching answers
Common stopping points
Continue from where the work stopped.
Choose the symptom you can see. We will take you to the closest verified answer instead of asking you to diagnose the system.
Task atlas
Start with the work, not our module names.
Each guide opens the page for a real logistics task and explains what the current module does before you enter the workspace.
01Prepare transport ordersTurn related emails, PDFs and images into a reviewable order draft.Order-entry guide02Check CMR and delivery proofMatch CMR or POD evidence and focus attention on missing or conflicting facts.Delivery-check guide03Extract transport permitsRead permit fields with source references and human review before export.Permit guide04Check files before invoicingReview the evidence behind charge candidates before invoice preparation.Billing-readiness guide05Prepare freight status updatesTurn verified events into controlled update drafts before sending.Status-update guide06Build emissions reportsCreate evidence-backed transport-emissions calculations and reporting outputs.Emissions guide
Verified answers
Practical guidance for the current product.
Search filters the answers below. Existing guidance remains visible to search engines and available without opening a support conversation.
Getting started
The Permit Parser accepts PDF, JPEG, and PNG files up to 10 MB each. You can select up to 20 documents in one batch and follow each file in the persistent batch queue.
No. The current release is a free, pre-commercial market-validation beta and does not offer checkout, subscriptions, or paid orders. Public prices are indicative and non-binding.
Permit processing & review
No. High-confidence fields that are not flagged are included automatically. The review opens on meaningful exceptions, so you only correct or confirm fields that need attention before approving the revision.
The review keeps the original permit authoritative and shows the source page, source wording, confidence, and validation reason for the selected field. Technical field paths are available under details when needed.
Approval locks the reviewed revision for export. The source document, corrections, reviewer actions, and export history remain linked for traceability.
Transport-emissions imports, calculations, evidence workspaces, reports and downloads are available to organizations with an active or trial module entitlement.
Plan & access
Open Dashboard → Settings → Plan & access. It shows the modules and limits currently assigned to your organisation. It does not provide checkout or create a payment obligation.
Organisation owners with member-management access can use Dashboard → Settings → Members & access. Invitations and roles remain scoped to the active organisation.
Use the contact form or support channel to describe your workflow. An enquiry records interest only; commercial service will be offered only after the required business and payment arrangements are in place.
Data & privacy
Core records are scoped to the active organisation and protected by server-side authorization and database Row Level Security. Access still depends on the role and capabilities assigned to the user.
Permit source files are stored privately and sent to OpenAI for extraction when you start processing. Extracted data remains a draft until human review; the original permit remains authoritative. See the Privacy Notice for provider and transfer details.
Try the task, not the error code
Use words such as upload, review, export, access or privacy.
Human support
Still blocked after the checklist?
Tell support what you were trying to finish and the status shown on screen. That gives us useful context without requiring your source documents.
Include the task you were trying to complete.
Include the visible status or error message.
Do not send passwords, API keys or unredacted sensitive documents in chat.