Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Ecommerce back-office integrations, with one system owning each record

When orders, stock counts, shipments and payouts sit in different tools, each tool keeps its own copy, and someone ends up retyping records and correcting totals by hand. We connect the store to your accounting, inventory and shipping tools around one owner for each record, set up alerts for failed runs and hand the connections to the people who run the store.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml builds the connections between the store, QuickBooks Online or Xero, the inventory or warehouse system and the shipping tool, records the system that owns each piece of data, watches for failed runs and leaves notes for your staff. The business itself stays with your team and its specialists.

Parts of a back-office integration

Before anything is connected, we agree which system owns each record: the product and its SKU, the stock count, the order, the shipment, the payout and the accounting entry. The other tools follow that owner instead of keeping a version of their own. Your store may need only some of the connections below.

Solution
Integrations
Connected systems
Shopify + WooCommerce + QuickBooks Online + Xero + Zapier + Make
Data flow
The store and its payment providers supply orders, refunds, products and payout reports. Orders that meet your release rules go to the warehouse or shipping tool, and shipment details return to the store. The inventory or warehouse system you name as owner keeps the stock counts, and the store's quantities follow it. Sales, refunds, fees and payouts reach QuickBooks Online or Xero in the form your bookkeeper approves. Every connection runs on Zapier, Make or a platform API and reports a failed or rejected record to the person responsible for it.
  • A map of which system owns each recordA written map of your tools, the connectors already installed and the places where staff retype or export data today. For each record, such as a product, a stock count or a payout, it names the system that holds the master copy and the person who answers for it. You approve the map before anything is built.
    01
  • Sales, refunds and payouts in your booksYour bookkeeper chooses whether each sale posts to QuickBooks Online or Xero on its own or within a payout summary, with refunds and fees accounted for. The chart of accounts and tax settings stay as your bookkeeper set them.
    02
  • Stock counts kept by one systemReturns, cancellations, write-offs and supplier deliveries are each recorded in one agreed system, which then sets the quantities the store shows. Stock at a third-party or overseas warehouse is included when its system reports quantities through an API, a connector or a scheduled file export.
    03
  • Orders passed to the warehouse or shipping toolOnce an order is cleared for shipping under your rules, it goes to your fulfillment partner's system or your shipping tool. Its acceptance and the tracking number are written back to the order. When an order is rejected, the reason goes to the person who can fix it.
    04
  • Alerts for the exceptions people act onAn alert for each case your team needs to handle: an order past your dispatch time, a connection run that failed, a record another tool rejected, stock under the threshold you set. Each alert names its owner and arrives where that person already works, such as an inbox or a team chat channel.
    05
  • Logged connections on Zapier, Make or an APIEach connection is built with Zapier, Make or the platforms' own APIs. Every run is logged, and records are matched on order numbers and SKUs, so a retried run doesn't create a second copy.
    06
  • Written notes for each connection's ownerYour team gets the map, the run logs and short notes for each connection: what it does, who acts on its alerts and how to restart a failed run. When you add a warehouse, a sales channel or a payment method, the map shows which connections it touches.
    07
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

Inputs and approvals the connections depend on

  • Your current tools and who looks after themThe store platform, accounting system, inventory or warehouse system and shipping tool, plus any apps, Zapier or Make accounts already moving data between them, and the person responsible for each.
    01
  • Access by invitation from your accountsStaff, collaborator or accountant invitations sent from your own accounts, so passwords stay with you. Where a tool limits invitations by plan, as Zapier does outside its Team and Enterprise plans, we agree the access route before work starts. Connector subscriptions are opened in your company's name and stay yours.
    02
  • Records that needed fixing by handA few recent orders, refunds and stock corrections that someone fixed manually, plus any report or spreadsheet that is compiled by hand. They show where the tools disagree and become the test cases.
    03
  • Your bookkeeper's approvalYour bookkeeper or accountant approves sample entries before anything posts and stays responsible for the accounts. The work covers QuickBooks Online and Xero; QuickBooks Desktop is outside it.
    04
  • The rules your team works byWhen an order is ready to ship, which warehouse handles which products, the stock levels that should raise an alert and who acts on each type of exception.
    05
  • A contact at your fulfillment partnerIf a third-party warehouse holds your stock, a contact there who can confirm how its system accepts orders and reports quantities.
    06

Tracing, testing and switching on the connections

  1. [Trace real orders through the tools]

    We follow the examples you sent through every tool and export, noting where each one was entered, copied or retyped. The result is a draft map of record owners for your approval.

    Step 01
  2. [Agree rules and test cases]

    With your team and bookkeeper we settle the release rules, the stock rules and the accounting form, then choose test cases from your examples: an ordinary order, a refund, a split shipment, a stock correction and a rejected handoff.

    Step 02
  3. [Build one connection at a time]

    Each connection is built and run on test records first, with emails to customers switched off.

    Step 03
  4. [Compare results with your examples]

    We run the test cases and check each tool against what your team and bookkeeper expected, including a deliberately failed run to confirm that its alert reaches the right person.

    Step 04
  5. [Release the connections in sequence]

    Connections go live one by one. We watch the first live runs with the person who owns each connection and go through the handover notes with your team.

    Step 05

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Back-office integration questions

Do we have to replace any of our current tools?
Usually not. The work starts from the tools you already pay for. Where two tools both change the same record, such as two apps that each adjust stock, we recommend which one keeps that job and switch the other off for that record once you approve.
Can you take over connections someone else set up?
Yes. We first document what each existing Zap, Make scenario or installed app does, which records it changes and whether its runs have been failing. Connections that work are kept; the rest are rebuilt or switched off once you agree.
Who fixes a connection that fails after handover?
The person named on the map gets the alert and the restart notes. A run that failed on a temporary error can be replayed from the Zap history, or retried in Make when the scenario is set to store incomplete executions. Changes to the connection itself can stay with your team, or Norml can look after the connections as separate ongoing work.
Should a connection use Zapier, Make or a direct API?
It depends on the connection. Zapier and Make suit records with clear rules and modest volumes, and your team can read and pause them. A direct API connection suits large catalogs, high order volumes or logic those tools handle poorly. We check each plan's limits and running costs with you before choosing.
Our store isn't on Shopify or WooCommerce. Does this still apply?
Yes, if your platform lets other tools read and update orders, products and stock through an API or a supported connector. What it allows on your plan decides how each connection is built, so we confirm that while drafting the map, before anything is connected.
What if the store and the warehouse show different stock counts?
We compare a sample of counts to find where they start to differ: an order deducted twice, a return never added back, a delivery entered in one place only. Each of those changes is then assigned to one system, and a scheduled comparison reports any gap that reappears.
Can stock still on its way from a supplier be included?
Yes, if it is recorded somewhere: a purchase order in the inventory system, or a shipment file from the supplier or freight forwarder. We agree how incoming stock is recorded and when it becomes available to sell. Arranging the shipment, customs and payment stays with your team and its partners.
Does Norml run bookkeeping, customs or supplier management?
No. Norml's part is the connections between your tools: building and monitoring them, passing them to your team and recording which system owns each piece of data. Bookkeeping, payroll and tax filings stay with your bookkeeper or accountant. Customs brokerage, tariff classification, duties and freight stay with your broker and forwarder. Supplier management, purchasing, customer service, the daily running of the business and the management of your staff stay with you.

Trace one order through your tools

Share a recent order, refund or stock correction that someone had to fix by hand, with the list of tools it passed through. We'll show where it was retyped and which connection would take that step over.

See all case studies