Solutions

What OMNI does and who it is for.

CB OMNI Enterprise 3PLs Brands Final Mile Components

Learn

Documentation, articles and a live walkthrough.

FAQs Wiki Blog Book a demo

The product

Every order, every building, every partner. One record.

CommerceBlitz OMNI is a data layer that sits on top of the systems you already run. Your channels, your warehouse software, your partners and your accounting connect to it, every order lands on one record, and everyone in the chain works their own view of that record.

  • What connects

    Your sales channels and marketplaces. Your warehouse system, or ours. Your 3PLs, dropship vendors and carriers. Your EDI trading partners on your VAN. QuickBooks or Xero.

  • What it holds

    Every order with its type. Every SKU with on hand and available to sell. Every shipment checked three ways. Every return with a reason. Every fee that attached to an order.

  • With CommerceBlitz OMNI

    One login and eight modules. Every person in the chain sees the slice their role allows, and the same numbers as everyone else.

For 3PLs, brands, distributors and the partners between them  ·  CommerceBlitz OMNI

Bolt on. Nothing gets ripped out.

It sits on top. Your warehouse system stays the on hand master. Your ERP stays the book of record. Your EDI keeps running through your VAN. CommerceBlitz OMNI connects to each of them, carries the order across, and hands back itemized orders, the PO reconciled against what shipped, and an audit log of who did what and when.

Where a system cannot connect, the record works around it. A file in and a file out, on the schedule the floor already runs. The order line does not wait for an integration project.

The CommerceBlitz OMNI order line page
This is the screen. Every order from every channel is a line on this page. Filter it to a client, a channel, a building or a PO number. Right click a cell and the filter builds itself. Send the view as a link and the person opening it sees only the fields their role holds.
The record

What goes in

01

Orders in from everywhere

Channels and EDI

With CommerceBlitz OMNI

Shopify, Amazon, Walmart, eBay, Etsy, Target and WooCommerce orders come in through turnkey connections attached from account settings. Retailer EDI comes in through the VAN you already run. The B2B order a sales rep emails gets keyed on the add order wizard with a type. Every one lands on the same line.

Today

Three doors in, three formats, three chances to get it wrong, and somebody retyping the emailed one into the warehouse system.

What the record holds

Every order with its type, its channel, its PO number and its fulfillment warehouse.

The integrations wall in account settings. Channels and carriers attach from here.
The integrations wall in account settings. Channels and carriers attach from here.
02

On hand is not available

ATS

With CommerceBlitz OMNI

The ATS report reads stock from every source, subtracts what is already committed and returns one available to sell number per SKU, by ship type. In the screen below, 7,928 on the shelf becomes 7,915 you can promise.

Today

The channel reads the shelf count, sells the thirteen units that were already spoken for, and the cancellation email goes out on Monday.

What the record holds

One number per SKU, pushed to every channel that sells it.

The ATS report: quantity on hand beside available to sell, with ship type and lead time.
The ATS report: quantity on hand beside available to sell, with ship type and lead time.
03

Rules per supplier, per brand

Balancer and Routes

With CommerceBlitz OMNI

For each supplier and brand you set which channels receive its inventory, which warehouses fulfill it, whether EDI and dropship apply, the dropship and restocking fees and the lead time. Balancer allocates by those rules. Routes assigns each order by cost, geography and service level, with a fallback.

Today

The split between channels lives in somebody’s head and a Friday spreadsheet, and the fallback is a phone call.

What the record holds

Who got to sell it and who shipped it, decided by a rule you can read rather than a person you have to ask.

The rule for one supplier and brand: channels, fulfillment warehouses, EDI, dropship, fees and lead time.
The rule for one supplier and brand: channels, fulfillment warehouses, EDI, dropship, fees and lead time.
04

The floor works by scan

Warehouse

With CommerceBlitz OMNI

Zones, moves, picking and shipping by scan, on your warehouse system or on ours. Pick tickets generate from a list of order numbers. The picking zone hands off to the shipping zone and the order line updates as it happens.

Today

The pick list is a printout, the move is a memory, and the cycle count is the first time anyone finds out.

What the record holds

What left the building, from which zone, scanned by whom.

Picking: scan the zone, scan the item, move it to the shipping zone.
Picking: scan the zone, scan the item, move it to the shipping zone.
The record

What comes out

05

Nothing ships twice

Routes

With CommerceBlitz OMNI

There is more than one point of failure between an order and a doorstep. Routes watches the warehouse system, the sales channel and the carrier account on every order. If tracking exists anywhere, even on an order a store shipped itself, it gets caught, logged and pushed everywhere it belongs, the order is marked shipped so nobody else ships it, and the carrier’s cost for that shipment lands on the order.

Today

Marked shipped in the channel but not in the warehouse system, or the other way round. It ships twice, or the tracking never reaches the buyer and the marketplace counts it late, and the freight cost turns up on a carrier invoice a month later with no order to match.

What the record holds

Every shipment matched three ways, with its cost on the order. The one that does not match is the only one you look at.

Quick filters on the order line: exported, cancelled, unfulfilled, partially fulfilled, fulfilled.
Quick filters on the order line: exported, cancelled, unfulfilled, partially fulfilled, fulfilled.
06

The return has a reason

Returns

With CommerceBlitz OMNI

The return is raised against the sales order and the SKU, with the next action and the reason on it. The replacement goes out as its own order, tied to the first one.

Today

A box on a shelf with a packing slip and no story, and a replacement order nobody links to the original.

What the record holds

Returns by reason, by SKU and by channel, with the replacement tied to the original.

Return to customer, refund or replacement, with the reason, against the original order.
Return to customer, refund or replacement, with the reason, against the original order.
07

Which channel pays

Reports

With CommerceBlitz OMNI

Orders, revenue, cost and profit by brand, vendor and channel, from the same record that shipped them. The download carries the columns you pick: cost, markup, dropship fee, EDI, warehouse, tracking, date of shipment.

Today

The marketplace report says one thing, the ERP another and the 3PL invoice a third, and somebody builds the channel view by hand.

What the record holds

Which SKU moves where, which channel drives cash and which drives top line, and what the fulfillment cost was on each.

The sales summary: orders, revenue, costs and profit for the period and the brands you pick.
The sales summary: orders, revenue, costs and profit for the period and the brands you pick.
08

Everyone sees their slice

Roles

With CommerceBlitz OMNI

A role is a checklist of what it can read, create, update and delete across brands, EDI, integrations, inventory, orders, products, reports, sales channels and shipments. A client, a partner warehouse, a delivery crew and a bookkeeper each get a role, a login and the same record.

Today

A shared login, a screenshot, or a weekly export, because the system cannot show one person less than everything.

What the record holds

Every action in the audit log against a named user, and every view limited to what that user’s role holds.

Roles management: what the Admin role can do, module by module.
Roles management: what the Admin role can do, module by module.

One login, eight modules.

Order View, Inventory Management, Order Management, Product Management, PO Management, Account Settings, Reports and Tools. The same login for your team, your clients and your partners; the role decides which of them a person sees.

Tools carries the pick ticket, inventory label and UPC label generators and bulk mark ship, so the floor’s paper comes off the record too.

The eight modules on the CommerceBlitz OMNI navigation
Who it is for

Pick your side of the record

The record is the same. The page that explains it is written for the seat you sit in.

  • 3PLs Every client, every building. One order line.

    A client portal, the order line and the billing, on top of the warehouse system you already run.

    Read the 3PL page
  • Brands Every channel, every warehouse. One record.

    Every 3PL, warehouse and dropship vendor you use works one record, and you read it as of now.

    Read the brand page
  • Final mile Deliver what your customer promised and prove it.

    One job record for the office, the crew, the client and the buyer at the door. Written for the operator and for the brand that ships heavy goods.

    Read the final mile pages
  • Enterprise Built to your network.

    Custom connectors, EDI partners on your VAN, principal and tenant accounts, on an annual term.

    Read the enterprise page
Beyond the order line

The engines under the record

The order line is what you read. Underneath it, four engines keep the stock, the channels and the routing honest. Each one answers a question, in order, and the next one works from the answer. The full write up of each engine is on the components page.

  • CommerceBlitz OMNI Aggregator
    What do we actually have?

    Inventory from vendor portals, distributor feeds, spreadsheets, APIs, FTP and email, parsed and cleaned before anything downstream reads it.

  • CommerceBlitz OMNI ATS
    What can we actually sell?

    The combined picture minus what is already committed, one number per SKU you can publish to every channel.

  • CommerceBlitz OMNI Balancer
    Who gets to sell it?

    One pool of stock allocated across storefronts by your rules, with thresholds that publish zero before an oversell.

  • CommerceBlitz OMNI Routes
    Who ships it, and did it ship?

    Each order assigned by cost, geography and service level, in a hierarchy you define, with a fallback. Then Routes watches the channel, the warehouse system and the carrier account. When a tracking number appears anywhere, the order is marked shipped so nobody else ships it, and the shipment cost comes in from the carrier and lands on the order.

  • Catalog sync and report card

    Products pull in from every channel and get checked for SKU and UPC problems. The owner fixes their own listings and resyncs.

  • Billing and rate cards

    Pick, pack, work order and special order fees itemized per client from the orders on the record, billed on your cycle, down to weekly.

  • Texts from the order, not from a phone

    Turn texts on for an order and the customer or the store gets the ship confirmation, the delivery window and a text when the order closes. Replies land on the order against the person who sent them.

  • White glove and final mile

    The delivery that needs a crew is a ticket on the same line, with the photos and the sign off. See the final mile page.

  • Accounting stays the book of record

    QuickBooks and Xero connect the same way the channels do. The record hands them itemized orders, not a reconstruction.

  • Ask instead of pulling a report

    Your team asks a plain question about inventory, orders or shipments and gets the answer. Runs in our own private cloud. Your data stays in.

Where each piece shows up on the platform.

  • Orders Every channel and every EDI order in one queue, filterable from any cell.
  • Warehouses Counts from your WMS, a client’s WMS or ours, resolved into one list per zone.
  • Billing One set of events, two rate cards, and why your client cannot be looking at different numbers than you.
  • Cash Flow Which part of a ninety day billing cycle is contractual, and which part you can shrink.
  • Integration Turnkey connectors, connections built for your stack, and inventory sync that starts switched off.
  • AI Most questions need one number rather than a dashboard, and reports built against your own fields.
  • Components The four engines and the warehouse system, in the order they answer their questions.

Where it sits

Bolt on. Nothing gets ripped out.

Warehouse system

Stays the on hand master. Pick, pack, what left the building. Where there is none, ours is light enough to stand up without IT.

ERP and accounting

The book of record. Handed itemized orders and fees, not a reconstruction.

EDI and channels

Your VAN, your retailer relationships and your storefronts keep working as they do now. The record reads them side by side.

CommerceBlitz OMNI carries every order across every building that fills it and every partner that touches it, and back to you as one record. A 3PL on the platform can give any client a portal. A brand on it can give any 3PL or carrier a working view. Either way, the next partner to join lands in a system somebody already uses every day.

This is what we are thinking. Tell us how it works with your business. If it works, great. If it does not, we both learned something.

Privacy Overview

This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.