Skip to content
LogCrew

Send one freight inquiry. Get comparable bids back the same day.

LogCrew puts your inquiry in front of vetted agencies matched by lane and mode, then carries the winning bid through award, bill of lading and invoice.

Sign in

Start an inquiry

Three fields, the same three an inquiry starts with.

Drawing your lane takes you to sign-up with these three fields carried across. Nothing is sent to an agency until you post the inquiry from your account.

Three things LogCrew does for a freight job

The same record carries the shipment from the first inquiry through to the invoice.

Inquiry fan-outExample— this panel is an illustration, not real customer data
1Agency AMiddle East · OpenedAgency BMiddle East · DeliveredAgency CEurope · DeliveredAgency DEurope · SentAgency EAsia · FailedAgency FAfrica · Pending
  • Opened
  • Delivered
  • Sent
  • Failed
  • Pending
One inquiry, one row per agency it reached, and the state the mail provider last reported for each. The agency names are placeholders; the states are the ledger's own.

One inquiry reaches every matched agency

Describe the shipment once. LogCrew matches agencies by lane, mode and region and sends the inquiry to all of them at the same time, instead of a separate email thread per agency that you then have to chase.

  • Auto-send by region, or hand-pick partners
  • Per-agency delivery status, so you know who actually received it
  • Failed sends retry on their own

Bids arrive somewhere you can actually compare them

Responses land against the inquiry that produced them — rate, proposed timeline and the agency behind each one, in a single sortable view. Awarding a bid moves the job forward and notifies the winner.
  • Every bid against the same inquiry, side by side
  • Award in one step; the agency is notified automatically
  • The job carries its own history from open to completed
Bid comparisonExample— this panel is an illustration, not real customer data
Three bids on one lane, sortable by agency, rate or transit time
Sample Forwarder LtdLowest rate$4,200.0026 daysWithin 4 weeks
Sample Logistics Group$4,650.0024 daysWithin 4 weeks
Sample Carrier CoFastest$5,100.0018 daysWithin 3 weeks
Sort by any column. The cheapest bid and the quickest one are rarely the same bid, which is the decision this screen exists to make.
Document lineageExample— this panel is an illustration, not real customer data

Hover or focus any document to see what the three of them share.

The reference and the lane are entered once, on the inquiry. The bill of lading and the invoice read them; nobody re-keys a port.

The bill of lading and the invoice come from the job

Generate both from the record that already holds the shipment details, so figures are never re-keyed between documents. Reconciliation runs against the originating inquiry rather than against a spreadsheet.

  • Bill of lading and invoice generated from one record
  • Customisable B/L template with your own branding
  • Download either as a PDF at any point

From inquiry to invoice, in one place

Every freight job runs the same six steps. LogCrew carries the same record through all of them.

The four states a job passes through

  1. 1

    Open

    Posted, not yet sent to agencies

  2. 2

    Bidding

    With agencies, collecting bids

  3. 3

    Awarded

    Won — in fulfilment

  4. 4

    Completed

    Delivered and closed

The six steps that move it

  1. Create an inquiry

    Submit origin, destination, cargo type and the delivery window. Agencies are matched by lane, mode and region.

    OPEN

  2. Send it out

    Auto-send to every matched agency at once, or pick specific partners. One inquiry, not one email thread per agency.

    OPEN

  3. Collect bids

    Responses land in a single comparable view — rate, transit time and the agency behind each one, side by side.

    BIDDING

  4. Award the job

    Pick a bid and award it. The winning agency is notified and the job moves into fulfilment.

    AWARDED

  5. Raise the paperwork

    Generate the bill of lading and the invoice from the job itself, so figures are never re-keyed between documents.

    AWARDED

  6. Close it out

    Record proof of delivery, reconcile payment against the originating inquiry, and close the job.

    COMPLETED

Four jobs the software takes off you

Each of these is a real afternoon, spent by a real person, on work that a record already holds the answer to. Pick one to see what does it instead.

Create inquiryExample— this panel is an illustration, not real customer data
  1. CompletedWhat are you shipping?
  2. Current stepWhere is it going?
    POL / Pickup location
    Jebel Ali
    POD / Delivery location
    Rotterdam
    Region
    Middle East
  3. Not startedWho should see it?
  4. Not startedBudget and timeline
Four steps, validated one at a time. The lane and region on step two decide which agencies are matched.

What the platform is actually doing

Four mechanisms, drawn rather than described. Each one is a system the backend runs, not an illustration of a shipping container.

  • Jebel AliOriginRotterdamDestination

    Sea freight

    An inquiry is a lane

    Origin, destination and one region. Those three fields decide which agencies the inquiry reaches.

  • 1Agency AMiddle East · OpenedAgency BMiddle East · DeliveredAgency CEurope · DeliveredAgency DEurope · SentAgency EAsia · FailedAgency FAfrica · Pending
    • Opened
    • Delivered
    • Sent
    • Failed
    • Pending

    Five regions, one send

    Auto-send blasts an inquiry to every agency in the chosen region. The list is the backend’s, not a menu we invented.

  • Recipient ledgerExample— this panel is an illustration, not real customer data
    Delivery state per agency for one inquiry
    AgencyRegionDelivery
    Sample Forwarder LtdMiddle EastOpenedDelivered and opened
    Sample Carrier CoEuropeDeliveredConfirmed at the receiving server
    Sample Logistics GroupAsiaSentAccepted by the provider, delivery unconfirmed
    Sample Brokerage LtdAmericasFailedRetried automaticallySend failed — retried automatically
    Sample Shipper LtdAfricaBouncedAddress needs fixingRejected permanently — address needs fixing
    One row per agency the inquiry was sent to, with the delivery state the provider reported back. Failures retry on their own; a bounce needs a person.

    Every send is tracked

    One ledger row per agency, carrying whatever the mail provider reported back. Retryable failures retry themselves; a bounce needs a person.

  • Record lineageExample— this panel is an illustration, not real customer data

    Hover or focus any document to see what the three of them share.

    The reference and the lane are entered once, on the inquiry. The bill of lading and the invoice read them; nobody re-keys a port.

    One record, three documents

    The bill of lading and the invoice are projections of the job, so a figure cannot disagree with itself between them.

What other people can see, and what they cannot

Three statements about how the software behaves. Each one is a mechanism you can point at, not a badge — and there is not a number anywhere in this section, because none of these are quantities.

  • Bidders cannot see each other

    A bid is visible to the agency that made it and to the agency that posted the inquiry. Nobody bidding on a job can read another bid on it, so nobody is pricing against a number they should not have.

    Enforced on the bid endpoints, not hidden in the browser.

  • The public feed is a different endpoint

    The lanes shown on this page do not come from the authenticated inquiry list with fields hidden client-side — that would still put the whole record on the wire. They come from a separate anonymised endpoint that drops parties, budgets and exact timestamps at the source, coarsens locations to port level, and returns nothing at all until there is enough recent activity for a row to be non-identifying.

    A dedicated public endpoint, read on the server.

  • Every send is on the record

    Sending an inquiry writes one row per agency and tracks what the mail provider reported back. You can see who received it, who opened it, and who never got it — and a retryable failure retries itself on a schedule rather than waiting for someone to notice.

    The recipient ledger, plus a scheduled retry job.

Questions people ask first

Find answers to common questions about LogCrew features, pricing, security, and more.

Ready to transform your logistics operations?

Put your next inquiry in front of matched agencies and compare the bids side by side.

Create an accountTalk to us first