How to Automate Runit

A chain's stock lives in several doors at once

Runit sells itself as Runit RealTime, a cloud system for specialty retail chains rather than for one shop. Apparel, footwear, sporting goods and gift, mostly, with several doors and often a warehouse behind them. That changes what the software is for. In a single store the stock question is do we have it. In a chain the question is where is it, which door is selling it, and is it worth moving. One style exists as a grid of colours and sizes multiplied by every location, and the same grid feeds a Shopify or BigCommerce storefront taking orders at midnight.

Runit holds the item, the customer, the transfer, the purchase order and the ledger in one place, with a business intelligence portal and visual dashboards over the top, and a phone app so an owner can look at yesterday from a car park. The people using it are a buyer, a merchandiser, a store manager, and whoever does the books on Thursday.

Every store has accounts nobody at head office opens

A chain accumulates logins the way it accumulates stock. Each store ships parcels, so there are tracking numbers on a carrier site that only the shipping manager ever looks at. Card-on-file and pay-by-link mean disputes, and a disputed transaction carries a representment deadline that lives on the processor's dashboard and nowhere else.

Wholesale and marketplace channels have their own back ends, with their own order status, their own returns and their own deductions. A mall lease usually obliges each store to certify monthly gross sales into the landlord's portal. Inbound freight has a container number and a port. None of that is retail either, and all of it is somebody at head office with fourteen tabs open on a Monday, copying figures into a spreadsheet that will be wrong by Wednesday.

Runit

Disputes found while the clock still runs The processor's dashboard read each morning with deadlines attached, so a representment is prepared inside the window rather than after it shuts.

Oversells caught before the pick Marketplace and wholesale orders set against what each door actually holds, so a channel sale is not confirmed on stock that went out yesterday.

Ship-from-store parcels with a real status Carrier pages checked and matched to the order that created them, so a delayed box is a phone call you make rather than one you take.

Auto Distribution moves what the chain already owns

Runit is unusually strong on the multi-store problem, and a chain not using this part is doing it by hand for no reason. Auto Distribution allocates a new model across the doors and rebalances sizes toward where they will actually sell, on rules the buyer sets, with the resulting distribution put up for the team to review before it commits. Transfers and warehouse management move stock between locations and out of the back. Purchase order management and receiving management cover what was ordered and what turned up against it. There is a real-time accounts receivable module, a general ledger, accounts payable, EDI integration for the vendors that support it, and ready-made e-commerce integrations for Shopify, BigCommerce and Magento. The business intelligence portal and its dashboards sit over all of it, alongside a report library deep enough that most chains never reach the end.

Every one of those works on stock the chain already owns, on an order it already placed, or through a partner Runit has connected to. The carrier holding the parcel is not one. Neither is the processor holding the dispute, the marketplace holding the wholesale order, the landlord's reporting portal, or the forwarder with the container.

Parcels, disputes and channel orders can answer for themselves

Put an agent on the accounts each store keeps outside the system, and head office hears about a problem while it is still small. Every open dispute read off the processor's dashboard each morning with its deadline attached, so a representment gets prepared inside the window rather than discovered after it closed. Ship-from-store parcels tracked on the carrier's own site and matched back to the order that created them, so the customer who paid by link is told about the delay before they ring the store. Marketplace and wholesale orders read from their own back ends and set against what Runit says is on hand at each door, so an oversell surfaces in the morning instead of at the pick.

Monthly gross sales assembled per store in the shape the landlord's portal asks for, ready to certify. Inbound containers followed to the port, so the buy that was meant to land in March is either confirmed or replanned while there is time. Sell-through by door pulled together before the vendor call rather than during it. Every one of those is a page a person can read, which is exactly what makes it a page an agent can read.

Head office keeps the decisions, not the tab-refreshing

A dispute has a clock on it, and whether to fight one is head office's call. So is a markdown, a transfer and a reorder.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens a carrier's tracking page, a processor's dispute dashboard, a marketplace back end or a landlord's reporting portal, reads what is there, and lays it beside the stock, orders and receivables already in Runit. Runs happen on a schedule you set, in your own private environment, and any run can be watched and stopped. Submitting a dispute response, certifying sales figures, moving a price or emailing a customer is prepared and left for approval. The workflows below name what each one opens.