Enterprise DNA

Instead of DirectSDS

Stop renting DirectSDS. Own your safety sheet distribution desk.

We build your version around your products, supplier documents and customer deliveries. Bring your agreed DirectSDS records across, then have Enterprise DNA run the system for you.

DirectSDS Pro for 4,000 safety sheets is listed at US$923 a month. Twelve monthly payments total US$11,076. Your actual plan and bill can differ.

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 DirectSDS bill

Document volume sets the subscription

The vendor lists US$923 a month for Pro at 4,000 safety sheets. That is US$11,076 across twelve monthly payments, before any difference in your contract or local charges.

paid

A library size band

The published plans scale with the number of safety sheets in your library.

layers

A plan for your distribution work

Basic, Premium and Pro package different document access and delivery capabilities.

sync

Delivery tied to orders

Premium includes delivery triggered by your business systems. Your installed version needs those connections scoped and tested.

update

Revision follow-ups

DirectSDS maintains customer update lists. An owned version keeps the obligations and delivery evidence together.

inbox

Supplier document intake

Pro adds a supplier inbox and automatic document intake. Human review remains part of our free desk.

link

Hosted document access

Exported permanent links still point to the vendor. A move includes securing your own supplier-issued copies.

Your version

A desk built around the sheet and the customer

First supply

See the document work behind every customer

Record the product, country and language once. Bring missing editions and first deliveries into the weekly review.

  • check Customer contacts and product codes kept together
  • check Separate Australian and New Zealand editions
  • check First supplies without delivery evidence listed clearly
  • check Customer requests linked to the exact obligation

Revisions

Follow the change all the way to delivery

A revised supplier document creates work for the affected customers. A pending revision stays visible until reviewed.

  • check Supplier versions retained with issue dates
  • check Unverified imports kept out of the approved set
  • check Pending revisions block use of the older edition
  • check Old delivery evidence retained beside the new obligation

Evidence

Keep proof separate from preparation

A prepared pack is a draft. A delivery needs the correct sheet and a reference to what actually happened.

  • check Supplier PDF copies retained with a document fingerprint
  • check Human review references recorded before use
  • check Product, country and language checked before recording delivery
  • check Internal customer packs and supplier follow-up sheets in your brand

Your questions

Join the records around the problem

Ask which overdue requests also have an unresolved revision, then follow the evidence to the supplier and customer.

  • check Ten ready questions across documents and obligations
  • check Read-only weekly, supplier and evidence reports
  • check Supplier review follow-ups grouped with affected customers
  • check Add your own fields and rules as the business changes

Make it yours

Design your own DirectSDS replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

SDS Distribution for Claude Code

Connected to your own database

Which customers still need a current safety sheet or delivery evidence?

Example Harbour Depot

Sku
DEMO-CLEAN
Country
NZ
Language
en
Version
demo-v2
Issue
Revision needs delivery evidence

Example Harbour Depot

Sku
DEMO-COOL
Country
AU
Language
en
Version
demo-old
Issue
Supplier review overdue

Example Harbour Service

Sku
DEMO-CLEAN
Country
AU
Language
en
Issue
No approved sheet

Example Valley Warehouse

Sku
DEMO-CLEAN
Country
NZ
Language
en
Version
demo-v2
Issue
First supply needs delivery evidence

Example Valley Warehouse

Sku
DEMO-WASH
Country
NZ
Language
en
Issue
No approved sheet

Ask it anything

Questions your distribution desk answers

Ten ready reports across supplier documents, customer obligations and delivery evidence. Each runs against the records in your own database.

chat_bubble Which customers have both overdue requests and outstanding revisions?
chat_bubble Which suppliers have unverified sheets with customers waiting?
chat_bubble Which customers need a different country edition of an existing product?
chat_bubble Which approved revisions have no recorded deliveries at all?
chat_bubble Which suppliers have ageing sheets still attached to customer obligations?
chat_bubble How many outstanding obligations does each customer have?
chat_bubble Which product and country combinations have multiple approved versions?
chat_bubble Which customer requests lack a usable current sheet?
chat_bubble Which customers have delivery evidence for an older revision only?
chat_bubble Which registered products have no customer supply records?

Switching

How to switch from DirectSDS

A move involves exporting and mapping your DirectSDS records, checking what imports, and reconciling customer obligations and delivery history before you retire the old service.

  1. 1

    Export your DirectSDS records

    Start with the XLS export DirectSDS documents, which contains product codes and permanent document links. Check with DirectSDS about what else your account allows you to export. Customer lists, subscriptions and historic delivery receipts are not included in the library import, so identify those records separately and plan how to reconcile them before ending your service.

  2. 2

    Prepare and map the records

    Prepare the documented extract as a CSV with the required eight columns, then map its columns to the fields in the new desk. Confirm country, language, revision and supplier details against your source records. Exported document links still depend on the vendor. Keep the actual supplier PDFs and establish links under your control before approving imported sheets.

  3. 3

    Test the import first

    Use the import test run to validate the prepared DirectSDS export without saving it. Review any problems it reports and correct the source or column mapping before importing for real. The import checks the whole file, rolls back if a row is bad, skips identical repeats and rejects conflicting versions. Compare the resulting record counts with DirectSDS before moving on.

  4. 4

    Reconcile flagged records

    Review every imported sheet, since imported sheets start unverified. Check that the supplier PDF, country, language, revision and supplier details are right, and resolve any flagged or conflicting records. Reconcile customer lists, subscriptions and historic delivery receipts separately because they are not part of the library import. Confirm customer obligations and delivery evidence before relying on the new desk.

  5. 5

    Run both, then switch

    Keep DirectSDS running alongside the new desk for a short period. Use that time to check that the records and customer obligations you rely on are accounted for, and have the delivery process and connections tested for your installed version. Once you have reconciled the records and confirmed the working process, retire DirectSDS. Keep the supplier PDFs and records you need.

construction

Where the real effort goes

The import is only part of the work. Most effort usually goes into mapping your own fields and supplier details, confirming product and customer rules, and deciding which customer obligations and delivery history to bring across and reconcile. Vendor-hosted document links are not owned copies, so supplier PDFs and controlled links need attention too. Enterprise DNA handles this mapping and setup when you have them run your version.

Not ready for a call?

Get your DirectSDS switch plan by email

We will send you the step-by-step plan for moving your business off DirectSDS, 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, customise it, or have it run for you

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm test and npm run demo with Claude Code, Codex, OpenCode or Cursor
  3. 3 Prepare your DirectSDS export as CSV and test its column mapping
  4. 4 Verify owned PDF copies, reconcile the records and test delivery evidence before switching
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your product fields, review rules and branded paperwork
  • check Your agreed DirectSDS records brought across and reconciled
  • check A web front end and customer access if you want them
  • check A different stack or delivery connections scoped around your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed, connected and operated through Omni by Enterprise DNA
  • check Document hosting, authorised delivery and team access built into the agreed setup
  • check Backups and operational checks tested around your records
  • check Ongoing changes as products, suppliers and customer needs change
Book a call with Sam

Questions

Instead of DirectSDS, answered

Does the free version send safety sheets automatically? expand_more

It prepares internal packs and records evidence of deliveries already completed through your authorised channel. It sends nothing. Enterprise DNA scopes and tests order connections, delivery and customer document access for your installed version.

Can we bring our DirectSDS records across? expand_more

DirectSDS documents an export containing product codes and document links. The free version imports a prepared copy after its columns and supplier metadata are mapped. Customer obligations and delivery history need separate reconciliation. Vendor-hosted links do not become owned documents just because you exported them.

Does this create or certify safety data sheets? expand_more

No. Your qualified suppliers provide the safety sheets. The desk records document review, keeps owned copies and highlights missing evidence. Your responsible people retain the chemical-safety decisions and review the applicable rules. Internal packs are not replacement safety data sheets.

What are we comparing with the DirectSDS price? expand_more

The cited Pro tier covers 4,000 sheets at US$923 a month. Twelve monthly payments are US$11,076. It is a published tier example, not a claim about your actual invoice. Bring your bill and the delivery functions you use so we can define the right replacement.

What does Enterprise DNA build into our version? expand_more

Your product mapping, supplier review process, customer access, delivery connections and team permissions. We bring across the agreed records, test the complete working process and run it through Omni by Enterprise DNA. One setup fee, then a retainer.

Own the work behind every safety sheet

Spend 30 minutes with Sam. Bring your DirectSDS bill, a sample export and the document deliveries your team handles each week. We will map the records and connections your version needs.

Book a call with Sam Get the free version

SDS Distribution for Claude Code is free and open source, published by Enterprise DNA.

Done paying for DirectSDS?

Get your version built