Enterprise DNA

Instead of SourceDay

Stop renting SourceDay. Own your supplier delivery desk.

We bring your SourceDay delivery records across, build your supplier review rules and run your version for you.

SourceDay pricing is quoted for your business. Bring your renewal and compare the delivery work you actually use.

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 the subscription covers

The delivery desk inside SourceDay

SourceDay combines supplier collaboration with connected order records. Start with the daily buying work you need to own, then scope the connections around it.

clipboard

Order acknowledgements

SourceDay tracks supplier responses. Your version shows the order lines still waiting for a recorded commitment.

calendar

Changing delivery dates

The supplier moves a date and the buyer must decide. Keep the original need date beside the accepted promise.

truck

Outstanding deliveries

Follow order quantities through partial receipts. A delivery docket reduces the balance without hiding the rest.

alert

Exceptions needing a buyer

SourceDay has order exceptions and planning views. Your daily review can join late promises with the follow-ups your buyer already owns.

chart

Supplier performance

SourceDay provides supplier reporting. Your scorecard separates measured completed deliveries from imported balances with unknown timing.

link

Connected supplier work

SourceDay connects suppliers and existing business systems. Enterprise DNA scopes those connections around your own records and approval rules.

Your owned version

Keep the evidence behind the delivery date

01 / Daily buying

A clear expedite list

Start the day with parts that need a buyer decision.

  • check Missed original need dates stay visible
  • check Promises beyond the need date are flagged
  • check Missing acknowledgements have named buyers
  • check Stale confirmations join the same review

02 / Supplier commitments

A promise is a recorded decision

Separate a proposed date from the date your buyer accepts.

  • check Supplier evidence stays with each proposal
  • check Acceptance and rejection record the buyer and reason
  • check The original need date stays unchanged
  • check Pending changes remain visible until decided

03 / Receiving

Partial receipts leave an honest balance

Record what arrived from the actual delivery evidence.

  • check Each receipt carries a docket reference
  • check Duplicate receipts and excess quantities are rejected
  • check Remaining quantities stay open for follow-up
  • check Imported balances have no invented delivery dates

04 / Your operating rules

Make the review fit your production week

Own the records, reports and rules behind the buying desk.

  • check Generate supplier follow-up drafts and receipt records
  • check Review supplier information and retention dates
  • check Add your own production references and escalation rules
  • check Join your follow-up history with original need dates in a report built for your business

Make it yours

Design your own SourceDay replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Supplier Deliveries for Claude Code

Connected to your own database

Which deliveries need attention today?

PO-4100/10/0

Supplier
Koru Components
Item
SEAL-40
Outstanding
60
Needed on
2026-10-28
Promise on
2026-10-30
Reason
need date missed

PO-4200/10/0

Supplier
Southern Fasteners
Item
BOLT-M8
Outstanding
500
Needed on
2026-11-02
Promise on
2026-11-05
Reason
promise beyond need

PO-4100/20/0

Supplier
Koru Components
Item
VALVE-8
Outstanding
20
Needed on
2026-11-04
Reason
acknowledgement missing

PO-4300/10/0

Supplier
Koru Packaging
Item
BOX-12
Outstanding
150
Needed on
2026-11-08
Promise on
2026-11-07
Reason
confirmation stale

Ask it anything

Ten questions your delivery records can answer

These answers come from the working demo. Your own fields and rules make the review specific to your business.

chat_bubble Which parts have missed the original need date despite a revised supplier promise?
chat_bubble Which open lines still lack a buyer-recorded supplier acknowledgement?
chat_bubble Which proposed dates are awaiting a buyer decision?
chat_bubble How many units are still due after each partial receipt?
chat_bubble Which accepted commitments have gone more than a week without reconfirmation?
chat_bubble Which follow-ups are overdue and who owns them?
chat_bubble Which suppliers delivered complete lines by the original need date?
chat_bubble Which imported balances have no receipt timing evidence?
chat_bubble Which records need retention evidence or a supplier purpose review?
chat_bubble Who accepted each promise and what evidence supported it?

Switching

How to switch from SourceDay

The move involves exporting your selected order views, mapping and checking the records, then running both systems side by side before you switch.

  1. 1

    Export your order views

    Use SourceDay’s documented Tab Export or View export to get CSVs for the order views you need. Include order lines, releases, quantities, dates and supplier details. Export what your account allows, then check with SourceDay if you cannot find the right view. Messages, attachments and detailed receipt history need separate mapping, so decide whether to bring them across.

  2. 2

    Map and load the records

    Check the real export against the required columns and map the date fields explicitly. The import accepts order lines, releases, quantities, dates and supplier details, with column mapping where needed. Validate the selected CSV view before loading it, then import the records. An exported promise date does not become a new supplier acknowledgement.

  3. 3

    Review the import results

    Review the validation results and any rows the import flags, then reconcile every release against your SourceDay view. Check quantities and dates, and confirm that the outstanding balances make sense. Imported received balances do not have receipt dates, so they should not be treated as dated receipt evidence. Messages, attachments and detailed receipt history need their own mapping and review.

  4. 4

    Run both systems side by side

    Keep SourceDay available while you use the new database for a short period. Compare the order lines, supplier commitments and outstanding quantities in both systems, and check that buyers can record the work they need. Review the original evidence behind dates and quantities. Resolve mismatches and refine your field mapping or rules before relying on the new records.

  5. 5

    Switch off SourceDay

    Once you have reconciled the releases and are satisfied that the new records support your delivery review, make the new system your working record. Confirm who owns updates and how supplier replies and receipt evidence will be recorded. Keep any SourceDay exports, messages, attachments or receipt history you still need in your controlled records, then stop using SourceDay.

construction

Where the real effort goes

Most of the work is mapping your fields and rules to the new records, then deciding how much history to bring across. Order lines and supplier details come from the selected CSV views, while messages, attachments and detailed receipt history need separate mapping. If you have Enterprise DNA run it, they handle the record mapping and reconciliation for your setup.

Not ready for a call?

Get your SourceDay switch plan by email

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

Do it 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, npm test and npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor
  3. 3 Export a SourceDay view as CSV, check the headers and test the import
  4. 4 Reconcile quantities and releases, then start the daily delivery review
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your supplier fields, production references and escalation rules
  • check Your SourceDay data mapped and reconciled before switching
  • check Your existing business connections and supplier response process
  • check A web front end or a different technology stack when your team needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with private evidence handling, access controls and backups
  • check Daily delivery reviews and supplier follow-up drafts prepared
  • check Connections and operating rules maintained as the business changes
  • check Run through Omni by Enterprise DNA alongside your other work
Book a 30-minute SourceDay review

Questions

Instead of SourceDay, answered

Can you bring our SourceDay orders across? expand_more

Yes. SourceDay documents CSV exports of selected order views. The free version imports order lines, releases, quantities, dates and supplier details from those files, with column mapping where needed. We reconcile your actual export before switching. Messages, attachments and detailed receipt history are mapped separately.

Will our suppliers have to use another portal? expand_more

The free version is a buyer-operated delivery record. Buyers enter supplier replies and receipt evidence. Enterprise DNA builds the supplier response process and any supplier screens your version needs, with clear approval rules.

Will this stay connected to our existing business system? expand_more

Connections are part of the custom scope. We agree which system owns each record, how updates move and who approves changes. The free version starts from exported records, so live order synchronisation is built and tested for your setup.

How do we know the dates and quantities are trustworthy? expand_more

The original need date stays separate from the accepted supplier promise. Receipts require a docket reference and cannot exceed the remaining balance. Imported received quantities carry no invented timing, and an exported promise does not become a fresh acknowledgement. Your buyer reviews the original evidence.

What do we pay Enterprise DNA? expand_more

One setup fee to build and bring across your version, then a retainer to run and improve it. We agree the scope around your actual supplier process and SourceDay renewal. The free version has no licence charge, with hosting and your chosen coding assistant paid separately.

Bring Sam one late order and your SourceDay renewal

In a 30-minute call, walk through the supplier promise, the receipts and the chasing. Sam will show what your own version needs and how Enterprise DNA can build and run it.

Book a 30-minute call with Sam Get the free version

Supplier Deliveries for Claude Code is free and open source, published by Enterprise DNA.

Done paying for SourceDay?

Get your version built