Enterprise DNA

Instead of Cargosnap

Stop renting Cargosnap. Own your cargo condition system.

We build your version around receiving, inspections and handovers, map your Cargosnap records across, and run it for you. Your release rules and evidence stay with your business.

Cargosnap lists €1,047 a month for 30 devices, billed monthly. That is €12,564 over twelve months at that rate. Compare it with the plan and device count on your own invoice.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The Cargosnap bill

You pay for the devices carrying the workflow

Cargosnap bundles its features across device plans. These are parts of that subscription, not six separate fees.

smartphone

Devices on the warehouse floor

The published plans scale by device count. The 30-device plan is €1,047 a month.

checklist

Forms and workflows

Custom workflows and digital forms are included in the subscription.

photo_camera

Photographs and digital proof

File management and digital proof are included features.

warning

Issue management

Issue management sits in the same plan as the inspection records.

groups

Team and customer access

Team management, unlimited users and a customer portal are included.

sync

Connections and offline capture

The plans include integrations and offline mode. Include those needs when comparing your replacement.

Your cargo records

From a condition check to an accountable handover

Receiving

Counts and seals checked together

Read the latest inspection beside the expected count and seal. Exceptions stay visible until someone deals with them.

  • check Receipt, packing and dispatch inspections
  • check Expected and observed package counts
  • check Seal mismatches shown with the shipment
  • check Condition history kept when a correction is added

Evidence

A damage record you can trace

Attach the original evidence and prepare a factual condition report for review.

  • check Each attachment tied to an inspection
  • check A file fingerprint to detect later changes
  • check Missing damage evidence listed explicitly
  • check A draft evidence summary with the shipment history

Ownership

Every exception has a person and a date

Review the unresolved work across your sites and carriers before the next handover.

  • check Named issue owners and due dates
  • check Overdue issues alongside stale cargo
  • check Carrier damage records beside unresolved issues
  • check Recorded resolutions retained in the history

Dispatch

Release follows your recorded checks

A release needs clear record checks and a sound dispatch inspection. Staff make the operational decision.

  • check Open issues block release
  • check A reviewer and reason recorded at release
  • check Handover receipt and accepting person retained
  • check Condition and handover reports in your own brand

Make it yours

Design your own Cargosnap replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Cargosnap. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Cargosnap replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Cargosnap data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Cargo Condition for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Cargo Condition for Claude Code

Connected to your own database

Which loads have a count, seal or condition problem?

CG100

Site
Auckland
Inspection
IN100
Condition
damaged
Units
116
Expected_units
120
Seal_check
match
Evidence_count
0
Open_issues
1

CG101

Site
Auckland
Inspection
IN101
Condition
sound
Units
80
Expected_units
80
Seal_check
mismatch
Evidence_count
0
Open_issues
1

CG102

Site
Melbourne
Inspection
IN102
Condition
sound
Units
40
Expected_units
40
Seal_check
match
Evidence_count
0
Open_issues
0

CG103

Site
Melbourne
Inspection
IN103
Condition
sound
Units
60
Expected_units
60
Seal_check
match
Evidence_count
0
Open_issues
0

CG104

Site
Auckland
Seal_check
missing
Evidence_count
0
Open_issues
0

CG105

Site
Melbourne
Inspection
IN105
Condition
unchecked
Units
100
Expected_units
100
Seal_check
match
Evidence_count
0
Open_issues
1

Ask it anything

Questions your cargo records can answer

Each question below runs against the fictional demo today. Your version follows your own receiving and release rules.

chat_bubble Which shipments have an unexplained seal difference?
chat_bubble Which receipts are short against the expected count?
chat_bubble Which damaged inspections still have no evidence attachment?
chat_bubble Which owner has the most overdue cargo issues?
chat_bubble Which carrier has damage records and unresolved issues together?
chat_bubble Which site has the most seal mismatches?
chat_bubble Which open shipments have not been inspected for a week?
chat_bubble Which shipments are waiting on a sound dispatch inspection?
chat_bubble Who accepted each recorded handover and what is its receipt reference?
chat_bubble What needs attention before the receiving desk closes today?

Switching

How to switch from Cargosnap

The move involves exporting form answers in manageable date ranges, mapping your fields and rules, then checking the new records alongside your current process before you switch.

  1. 1

    Export your Cargosnap records

    Cargosnap form exports provide answers in an Excel spreadsheet, with one column per question and a date range of up to 30 days at a time. Agree which history to bring across, then export those form answers. Photographs need to be downloaded separately. Form answers do not include the complete workflow history, so check with Cargosnap about a broader export if you need it.

  2. 2

    Load a reviewed sample

    Have the exported answers mapped to the matching fields in Cargo Condition. Start with one reviewed month rather than importing all the history at once. Compare the submission count with Cargosnap and check that the answers landed in the right places before loading more. This gives you a chance to correct the mapping before it affects the rest of the records.

  3. 3

    Check the imported records

    Review the import results and resolve anything that did not come across as expected. Check submission counts, field mappings and the records you rely on for inspections, issues and handovers. Make sure separately downloaded photographs are matched to the right inspections. If you are bringing broader workflow history, review that mapping too, since form answers alone do not contain the full workflow.

  4. 4

    Run both processes together

    Keep your current Cargosnap capture process while you test the replacement with your team. Compare new records and evidence in both systems, and check that the reviews and handovers your operation needs are covered. Use this period to find gaps in fields or rules and correct them before you rely on the replacement. The current capture process can stay in place while the replacement is built and tested.

  5. 5

    Switch off Cargosnap

    Once your team has checked the imported history and tested the replacement process, agree when to stop using Cargosnap. Confirm that the records and photographs you chose to bring across are available, and that your team knows how to continue its capture and review work. Keep the agreed exports according to your own recordkeeping needs.

construction

Where the real effort goes

The main work is mapping each Cargosnap form question to your fields and rules, deciding which history to bring, and handling photographs separately. Form exports cover answers, not the complete workflow history. If Enterprise DNA runs the replacement, they do this mapping and import work with you.

Not ready for a call?

Get your Cargosnap switch plan by email

We will send you the step-by-step plan for moving your business off Cargosnap, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free base or have your version built and run

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, install it and run npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for the condition round
  3. 3 Map your Cargosnap form questions, test the XLSX or CSV import, then reconcile the records
  4. 4 Attach downloaded evidence and set up your database and backups
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your receiving forms, condition grades and release rules
  • check Your Cargosnap exports mapped and checked against the originals
  • check Phone capture, offline work or a customer screen built for your operation
  • check Your preferred database and connections to the systems you keep
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access and backups for records and evidence
  • check Receiving exceptions and overdue work prepared for review
  • check Your inspection and handover process maintained as it changes
  • check Operated through Omni by Enterprise DNA alongside your business
Book a call with Sam

Questions

Instead of Cargosnap, answered

What does the free version do today? expand_more

It records shipments, inspections, local evidence, issues and handovers. It checks counts and seals, lists overdue work, prepares branded reports and records dispatch decisions. The examples below run on fictional demonstration records.

Can you bring our Cargosnap history across? expand_more

Yes, with the export and reconciliation agreed first. Cargosnap exports form answers to Excel, with one question per column and a date range of up to 30 days. We map those questions and test the import. Photographs are downloaded separately; complete workflow history needs a broader export and mapping.

What about phones, offline capture and our customer portal? expand_more

We build those parts into your version around the way your team works. Keep your current capture process while the replacement is built and tested. The free base works with imported form records and evidence saved on your own storage.

Does a clear check mean the cargo is safe or a claim is valid? expand_more

No. The checks show gaps and differences in your records. Trained staff inspect, decide and review any claim. The condition and seal guidance is cited, and local release rules are labelled separately. A recorded handover receipt is not an authenticated signature.

How do we compare the cost? expand_more

Bring the current invoice, device count and the capture work you need. Compare the subscription with owning your system and having Enterprise DNA build and maintain it. Our offer is one setup fee, then a retainer; the scope is agreed around your operation.

Bring your Cargosnap invoice and a real receiving form

Spend 30 minutes with Sam. Walk through a damaged load, the evidence your team collects and the decision before dispatch. We will show you what your own version needs and what it takes to run.

Book a call with Sam Get the free version

Cargo Condition for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Cargosnap?

Get your version built