For physical-world operations
Operational decisions in supply chain, logistics, and field work need human sign-off with a record, often across organizations. Velt puts that sign-off inside your product: approval workflows on the record and its fields, comments scoped to your team or the counterparty, and notifications that reach reviewers in the yard, not just at a desk.
Free tier. No credit card. First comment in 5 minutes.
Cotton Supplier Ltd.
AgriCotton Farms
Village Kheda, Gujarat, India
SpinCo Yarns
18 Narol Rd, Gujarat, India
DyeWorks International
Calle de Mayo, Mexico
Can you attach the GOTS cert for this lot before we approve? @Sean
1 ReplyThe review reality
If your product moves orders, shipments, or work orders that someone in another organization has to sign, this page is for you.
A shipment sat at the dock for two days because the release approval sat unread in an inbox, with no way to escalate it inside your product.
A counterparty read an internal note about their own rates, because your product has one comment stream for everyone instead of threads scoped to the team.
The field crew never saw the inspection request, because they work from phones in a yard, not from a desk inside your web app.
A customer audit asked who approved the substitution on the manifest, and the answer lived in a text thread on someone's phone.
The loop
Velt runs one change order from filed to signed inside your product: a review agent first pass on the rate, comment threads scoped to each side, a staged approval chain that crosses the org line, notifications that reach the field, and an audit record of every decision. Both humans and agents act through the same primitives; nothing changes without a human accepting it.
// one change order, six steps, one record. Both orgs sign off without leaving your product.
The carrier cannot meet the delivery window, so the counterparty files a change order against the shipment record inside your product. The thread anchors to the record itself, not to an email about it.
A review agent checks the change order against the contract terms and leaves a comment pinned to the rate line: the revised rate is 9% over the contracted lane rate, flagged for commercial review. Approve and Reject are attached; the finding is advisory, and a human decides.
Revised rate is 9% over the contracted lane rate.
Two threads live on the same record. The internal thread, badged internal, debates absorbing the cost versus disputing the rate, and the counterparty cannot see it. The shared thread asks the counterparty to confirm the new delivery date, and they reply in your product instead of in an email chain about it.
Internal: margin holds at 1,450. OK to confirm. INTERNAL
The workflow routes the record: the ops lead approves, commercial approves the rate exception, then the counterparty's signer records the final decision. Both sides are users your product provisioned with access to this record, and every transition is timestamped and attributed.
The site supervisor gets the request by email, opens the record on mobile web, and approves from the yard. The counterparty's signer is notified of the shared thread and their step only, because notifications generate solely for what each user can access.
The full chain sits in one place: who was asked, who decided, and what changed on the record, queryable by document, user, or time range, and exportable when the customer audit comes.
Feature map
Each card links its feature page. Preview the UI, or read the code that renders it.
<VeltApprovalFlow
stages={["ops", "commercial", "counterparty"]}
/>Release chains, rate exceptions, and change order sign-off: your customer's steps first, the counterparty's signer last. Approve advances the record; reject routes it back with every prior attempt attached.
Explore Approval flowsAnchored to the rate line on the manifest: not a screenshot of it.
<VeltComments />Threads on the order, the manifest, and the field record. Internal deliberation stays scoped to the team; the counterparty reads only the thread meant for them.
Explore CommentsSign-off request · release the holdsent
access-filtered delivery
<VeltNotificationsTool />The sign-off request leaves the building: in-app for dispatch, email for the yard, access-filtered so each organization sees only its own activity.
Explore NotificationsPOST /v2/activities/get
{ "data": { "documentId": "ship-4127" } }Who released the hold, who approved the substitution, and what changed on the manifest, queryable by record, user, or time range, and exportable when the customer audit lands.
Explore Audit trailin the work order now · before two people release the same hold
<VeltPresence />See who is in the work order right now, your dispatcher or theirs, before two people release the same hold.
Explore PresenceAgent action layer
An agent that reconciles a manifest against the order is a tireless first-pass reviewer. An agent that corrects the manifest on its own is a liability with a loading dock. In Velt, every agent finding lands as a comment with Approve and Reject attached. On approve, the correction applies through your webhook with a permanent record of who allowed it; on reject, nothing moves and the rejection is logged. The agent never holds write access to orders, inventory, or the counterparty's data. The stakes in operations are physical: a bad automated write is not a rollback, it is a truck at the wrong dock, a crew on the wrong site, a counterparty reading a number they were never meant to see.
Flags · manifest line 14 does not match the order quantity
Audit entry
Approved · Dispatcher · Tue 09:14 · manifest corrected · agent never held write access to orders
on reject, nothing moves and the rejection is logged
In production
Operations platforms run sign-off on orders, shipments, work orders, and change orders across organizations, where the reviewer is often in a yard, a truck, or a job site rather than at a desk. They embed approval chains, visibility-scoped comments, and the audit export their customers' auditors ask for, instead of routing release decisions through phone trees and forwarded email.
See it running in products like yours.
30 minutes, with an engineer, not a sales deck.
Compliance
In operations the leading concern is what crosses between organizations, so the strip leads with residency and counterparty visibility.
Per-thread visibility scopes and access-filtered notifications decide what crosses the org line. Internal activity stays internal, and notifications generate only for the documents and threads a user can access.
Data residency options including the EU. Self-host data providers keep order, shipment, and comment content plus user PII on your infrastructure, while Velt stores minimal identifiers.
Self-hostingSOC 2 Type II, with immutable review records and export for customer audits.
GovernanceEnforcement wording and certifications beyond SOC 2 Type II are verified with engineering before they render.
FAQ
Yes, when both sides are users in your product. Your product provisions the counterparty's reviewers as users with access to the shared record; the workflow routes steps to either side's people in order, and every decision is timestamped and attributed. Internal-only threads and notifications never reach them.
Yes. Any thread can be scoped to the author, the team, or specific people, and notifications generate only for documents and threads a user can access. The counterparty sees their shared thread move; your customer's internal deliberation never reaches their inbox.
Velt is optimized for mobile web, works inside WebViews in native apps, and pure native apps can integrate through the REST APIs with your own native UI. The request also travels out of the product: email through your SendGrid account or any service via webhooks, and your own channels via webhooks.
Yes. A document in Velt is any unit of work your product renders: an order, a shipment record, a work order, an inspection. Comments anchor to records and fields, approvals attach to the record, and the audit trail follows it.
The record. Every comment, approval, and rejection is captured automatically with who, what, and when, queryable by document, user, or time range, and exportable. The answer to "who approved the substitution" is a query, not an archaeology project.
Velt is priced on usage, not seats: you pay for documents with review activity in a month, so occasional counterparty reviewers do not multiply your bill. There is a free tier for development and early production.
Free tier. No credit card. First comment in 5 minutes.
30 minutes, with an engineer, not a sales deck.