Nov 11AI vendor breach exposes Notion AI chat transcripts.Why it matters

New software, set up around how you actually run.

Katana, ShipStation, Sutton, RepZio, and more. We configure it, import your data, train your team, and then automate around it.

Built and run by DataAutomation

YouIs our data ready for go-live on Monday?

Old system1,214 products exportedready
Spreadsheet38 products have no unit costgaps
New systembills of materials importedloaded
DA rulego-live check: costs requiredheld
DataAutomation assistantAlmost. 38 products have no unit cost, so their margins would show as 100% after go-live. Fill them in from the last purchase price, or review them with your team first?
About 2 weeks

typical go-live

As long as there are no delays on the client side.

A new system is only as good as how it is set up. Settings copied from a sales demo, data migrated with its old mistakes, and training on screens instead of real work are why so many setup and migration disappoint.

We implement Katana, ShipStation, Sutton, RepZio, and more, around how you actually make, buy, sell, and ship. We clean your data before it goes in, train your team on their own transactions, and plan the integrations around the system from the start.

Where it earns its keep

The biggest win is clean data on day one: products, variants, recipes, suppliers, and stock imported correctly, so costs and stock are right from the first order.

The second is a system connected to everything around it. An inventory system that does not get orders automatically is just another place to re-type.

Common use cases

What clients usually start with.

Off spreadsheets and into a real system

Products, recipes, and stock moved from spreadsheets into Katana or another system, cleaned on the way.

One place to plan from.

Variants and SKUs that scale

A variant structure and SKU pattern built from what makes each item different.

New options fit without a rebuild.

Recipes that cost correctly

BOMs with the right units, sub-assemblies, and operations.

True cost per unit from day one.

Shipping set up around how you ship

ShipStation stores, carriers, packaging, and automation rules configured to your real rules.

Labels print right the first time.

Training on real work

Your team trained on the transactions they do every day.

Adoption that sticks.

Connected from the start

Store, accounting, and shipping connections planned with the setup.

The new system becomes the source of truth.

Where it gets complicated

What usually goes wrong, and what we do about it from day one.

  • Configuring the demo, not the business

    Sales demos show a tidy company. Setups copied from them miss how you really make, buy, sell, and ship, and the team quietly goes back to spreadsheets.

    We start from a walk-through of your actual process and configure to it, screen by screen.

  • Migrating the mess

    Duplicate SKUs, wrong units of measure, and dead items copied across become the new system’s problems, and costs are wrong from the first order.

    We clean and restructure your data before import, and check it against the system’s rules.

  • Training on screens, not on work

    Generic training shows where the buttons are. People forget it by Monday.

    We train each person on the transactions they do every day, using your own products and orders.

  • Connections left for later

    A new system that does not get orders automatically is just another place to retype. Leaving connections for "phase two" is how that happens.

    We plan store, accounting, and shipping connections during setup, so go-live is connected.

What you get

  • A setup plan

    Settings, structure, and data decisions written down before anything is configured.

  • Clean, imported data

    Products, variants, recipes or packaging, suppliers, customers, and opening stock.

  • A configured system

    Locations, units, workflows, documents, and permissions set to how you run.

  • Team training

    Role-by-role sessions on real transactions, recorded for new hires.

  • Go-live support

    Us on hand for the first weeks to answer questions and fix what surprises you.

  • A plan for what comes next

    The integrations and automations worth adding, in priority order.

What a typical project looks like

  1. Week 1: map and clean

    We walk through how you work, collect your data, and fix duplicates, units, and naming before anything goes in.

  2. Week 1 to 2: configure and import

    Settings, products, recipes or rules, and opening stock loaded in the right order, then checked.

  3. Week 2: train

    Each role trained on their own work in the new system.

  4. Go-live and after

    You switch over with us on hand, and we stay close for the first weeks. Typical go-live is about 2 weeks, as long as there are no delays on the client side.

Our full process →

Is this right for you?

A good fit if

  • You are moving off spreadsheets or an old system
  • You bought the software and setup has stalled
  • You want the new system connected to your store and books from day one

Probably not the right fit if

  • You have not chosen a system yet (start with fractional CAIO or CTO)
  • The software vendor’s own onboarding covers what you need (try it first)
  • You need a platform we do not implement (we will tell you, and who does)

Pricing

Katana

Setup, configuration, imports, and training.

$2,300

Katana full setup

Everything imported for larger catalogs: $0.10 per data line, $4,000 minimum (50,000 lines is $5,000).

From $4,000

ShipStation, Sutton, and RepZio

Setup, configuration, imports, and training.

From $3,000

See all pricing →

A note on trust

We have been audited by Deloitte and PwC, and we complete Amazon's SP-API security assessment. Your data stays in your systems, approvals are set to how much you want automated, and every automated step is logged. See our audits →

Questions

Which platforms do you implement?

Katana, ShipStation, Sutton, RepZio, and more. See the Partners page for details.

How long does it take?

About 2 weeks on average, as long as there are no delays on the client side.

Can you move us off spreadsheets or another system?

Yes. We map and clean your data first, then build the import.

What is the difference between the $2,300 Katana option and the full setup?

The full setup is for larger catalogs where we import everything: $0.10 per imported data line with a $4,000 minimum, so 50,000 lines is $5,000. We help you pick on a quick call.

Do you work with consultants?

We work directly with your team. If you are working with a consultant, tell us up front so we can agree how decisions get made.

Can you implement and integrate together?

Yes, and it is usually the best way. We plan the integrations while we set up the system.

Do we need to clean our data first?

No. Cleaning is part of the work. Send it as it is.

What does it cost for a large catalog?

For Katana, the full setup is $0.10 per imported data line with a $4,000 minimum, so 50,000 lines is $5,000.

Can you fix a setup someone else did?

Yes. We review it, list what to change, and fix it with your team.

Audited every year.

Deloitte and Amazon SP-API audits in 2026. PwC and Amazon SP-API in 2025. Shadow AI was involved in 43% of the breaches IBM studied for its 2026 report; we keep your data out of it. And if something we run goes wrong, we own the fix.

See the latest AI incidentsSee our audits