Enterprise DNA

Instead of Opendock

Stop renting Opendock. Own your dock appointment system.

We build your version around your sites and receiving rules, bring your Opendock appointment history across and run it for you. Your schedule and operating evidence stay in a database you own.

Opendock asks buyers to request a demo. No public tariff was found. Compare your actual renewal and included services with the work your own version needs.

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

What you are paying for

Separate the dock records from the services around them

Opendock provides hosted scheduling and reporting. Start with your actual agreement, then decide which records, booking services and connections your own operation needs.

warehouse

Warehouse setup

Your warehouse settings, load types and appointment fields shape the schedule. Your own version can follow the receiving rules your team actually uses.

calendar_month

Dock calendars

Opendock supports operating windows and dock capacity. We agree your capacity rules before moving an active schedule.

local_shipping

Carrier booking access

The hosted carrier portal is a service to account for in the comparison. Enterprise DNA scopes carrier access for the version built for you.

notifications

Appointment notifications

Opendock includes event notifications. We connect the communications your own workflow needs, with the approvals you choose.

analytics

Reports and exports

Opendock already offers custom reports and exports. Owning the records lets you combine them with your own shift notes and evidence rules.

folder

A history worth keeping

Bring the selected appointment history across, preserve the source records and check them against the live receiving plan before switching.

Your own receiving desk

A schedule with evidence behind it

PLAN

Prepare the next shift

See the loads still due and resolve collisions before the receiving team takes over.

  • check Appointments grouped by site and dock
  • check Planned times in each site’s local timezone
  • check Overlapping bookings flagged for review
  • check A named owner beside the load

MOVEMENTS

Keep the actual times

Separate what was booked from what the operator observed at the site.

  • check Arrival, loading, completion and departure recorded separately
  • check Waiting time calculated from recorded observations
  • check Time beyond the agreed allowance shown for review
  • check Missing observations left visible instead of guessed

EVIDENCE

Know what supports the record

Bring loading observations, traffic-plan reviews and schedule decisions into the same history.

  • check A named loading-zone controller
  • check Evidence of load information and vehicle restraint checks
  • check Driver briefing and exclusion-area observations
  • check Original imports retained beside later decisions

HANDOVER

Give the next person a usable record

Prepare a shift handover and appointment evidence record in your business name.

  • check Open loads and exceptions for each site
  • check Carrier arrival and waiting-time comparisons
  • check Draft carrier notes for manual review
  • check Your own evidence rules added as the operation changes

Make it yours

Design your own Opendock replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Opendock 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 Opendock 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 Dock Appointments for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Dock Appointments for Claude Code

Connected to your own database

Which appointments need a decision now?

APT-101

Site
HARBOUR
Dock
IN-1
Carrier
FERN
Owner
Rae
Reason
Arrival overdue
Detail
2026-11-11 09:08

APT-102

Site
HARBOUR
Dock
OUT-1
Carrier
RIDGE
Owner
Jules
Reason
Detention review
Detail
124 minutes beyond agreed free time; not a charge

APT-104

Site
HARBOUR
Dock
IN-1
Carrier
FERN
Owner
Rae
Reason
Dock conflict
Detail
Overlaps APT-103

APT-103

Site
HARBOUR
Dock
IN-1
Carrier
RIDGE
Owner
Rae
Reason
Missing reference
Detail
Confirm the shipment reference

APT-104

Site
HARBOUR
Dock
IN-1
Carrier
FERN
Owner
Rae
Reason
Request unapproved
Detail
2026-11-11 14:38

Ask it anything

Questions Opendock cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which appointments need a decision before the next shift?
chat_bubble Which imported bookings overlap on the same dock?
chat_bubble Who is waiting beyond the free time we agreed?
chat_bubble Which completed loads have no recorded departure?
chat_bubble Which carrier has late arrivals and missing observations?
chat_bubble What is due at each dock in the site’s local time?
chat_bubble Which loading records have no safety evidence?
chat_bubble Who changed an appointment and why?
chat_bubble What did the source export say before a later revision?
chat_bubble Which sites have old exports or no export at all?

Switching

How to switch from Opendock

A move usually involves exporting the appointment history you want, mapping it into the new database, checking the imported records and running both desks side by side before you stop using Opendock.

  1. 1

    Export your appointment records

    Ask Opendock for an appointment export with the fields you need. Opendock documents selectable appointment export fields, but the available options depend on your account, so export what your account allows, usually CSV or Excel, and check with Opendock if you are unsure. Decide which appointment history you need to retain before choosing the fields.

  2. 2

    Test the import

    Map the export fields to the new desk's appointment fields, and make sure the site's docks and carriers are registered. Run the import as a test first so it previews the records without writing them. Check the mapping against your actual export, not a sample, before loading the records for real.

  3. 3

    Review import issues

    Review every issue the import reports before treating the records as ready. The importer rejects unknown statuses, missing appointment IDs and timestamps without time-zone offsets, while overlapping imported bookings are kept for reconciliation. Fix the source data or mapping where needed, then reconcile record counts and appointment times against the Opendock export. Records without arrival or departure observations remain incomplete.

  4. 4

    Run both desks side by side

    Keep Opendock available and use the new desk alongside it for a short period. Compare upcoming appointments, dock assignments and movement records in both systems, and resolve differences before making the new desk the one your team relies on. Agree who updates each system during this overlap so staff do not mistake an unverified record for the current schedule.

  5. 5

    Switch off Opendock

    After you have reconciled the records and your team is ready to work from the new desk, stop entering new appointments in Opendock and switch your operating process over. Keep a full export and a tested backup of the new database, and confirm your team knows where to find the appointment and shift records. Follow your Opendock account terms for ending service.

construction

Where the real effort goes

Most of the work is matching your Opendock fields to the new records, setting up your docks, carriers and booking rules, and deciding how much history to bring. Older records without arrival or departure observations stay incomplete, so choose history with that in mind. If Enterprise DNA installs and runs your version, it inspects the export, maps the fields, imports the records and reconciles counts and times with you.

Not ready for a call?

Get your Opendock switch plan by email

We will send you the step-by-step plan for moving your business off Opendock, 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

Run the desk yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and review the dock plan
  3. 3 Map your Opendock appointment export, preview the import and reconcile the counts
  4. 4 Set your site rules and operate the desk on a database you control
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your sites, loading windows, capacity rules and evidence requirements
  • check Your Opendock appointment records mapped and checked
  • check Carrier booking access and a web front end if your team needs them
  • check Connections and a different technology stack where your business requires it
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 agreed
  • check Appointment imports and shift review work operated with your team
  • check Connections and reports maintained as the operation changes
  • check Run through Omni by Enterprise DNA, beside the rest of your business
Book a 30-minute call

Questions

Instead of Opendock, answered

How does this compare with our Opendock bill? expand_more

Use your actual renewal and the services it includes. No public Opendock tariff was found, so we do not put an invented price beside yours. Enterprise DNA builds and runs your version for a setup fee then a retainer. The do-it-yourself version is free to use, with hosting and operation still your responsibility.

Can our appointment history come across? expand_more

Opendock documents appointment exports with fields you select. We inspect your export, map the fields, bring the records across and reconcile the counts and times. A record without an arrival or departure observation stays incomplete. Files, permissions and booking rules are scoped separately.

Can carriers book their own slots? expand_more

Enterprise DNA can build carrier booking access, shared screens and notifications into your version. We agree those needs before the switch. The free base is an operator-run receiving desk, useful when your office manages the schedule.

Will it calculate detention charges or certify safe loading? expand_more

It shows waiting time and minutes beyond the allowance entered for the appointment. A person checks the actual contract before agreeing a charge. Loading checks identify missing recorded evidence. The site’s people and physical controls remain responsible for safe operations.

Can we keep our own rules and change the system later? expand_more

Yes. Your appointments and history sit in a database you own. We can add your capacity rules, references, evidence checks and connections. Keep a tested backup and a full export, and agree the access your team needs.

Bring your Opendock renewal and a sample of the schedule

Book 30 minutes with Sam. Walk through your sites, current bill, appointment exports and the services your team needs. Agree what your own version should do first.

Book a 30-minute call Get the free version

Dock Appointments for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Opendock?

Get your version built