Your store and your ERP are strangers, and your customers can tell

You did the modern thing and put your catalog online — Shopify, or Magento, or both. Sales come in. And then, every morning, someone opens the store's order list and re-types those orders into Ross by hand, because the two systems have never been formally introduced. Meanwhile the store cheerfully sells things you don't have, because it's working off an inventory number that was last accurate at some point in the past, and the customer finds out you oversold when you email them an apology instead of a shipment.

This is the most public version of the disconnect, which is what makes it sting. You put the catalog on Shopify or Magento; Ross never found out — so the store oversells, orders get re-keyed by hand, and customers see stock you don't actually have. Everyone else's integration problems are internal. This one happens in front of the people paying you.

Why Ross and e-commerce are natural strangers

Ross was designed decades before "check out and pay in real time on a phone" was a requirement, and it shows. It's a system of record built for orders, inventory, and finance on the company's terms and the company's clock — not for a public storefront hammering it with reads and writes at 2 a.m. on Black Friday. So the two live in different worlds: the store wants current answers right now, and Ross wants transactions posted correctly and in order.

Bridging them means mapping four things carefully — products, pricing, inventory, and orders — across systems that model each of them differently. That mapping is exactly the work, and it's exactly what gets skipped when someone promises a "quick connector."

Inventory is where you embarrass yourself

If this integration is going to hurt you publicly, it'll be through inventory, because overselling is a customer-facing failure with a receipt attached.

The store can only be as honest as the inventory number it's given. If that number is a nightly snapshot, then all day long the store is selling against yesterday's stock — and in a business with real production, lots, and allocations, yesterday's stock is a work of historical fiction by lunchtime. The fix is keeping the store's available-to-sell figure close enough to Ross's reality that you stop promising product you've already shipped to someone else. That's a sync-frequency and allocation problem, and it's the difference between "temporarily out of stock" (fine) and "we took your money for something that doesn't exist" (not fine).

Orders have to flow in, cleanly

The re-keying ritual isn't just tedious — it's a defect factory. Every hand-typed web order is a chance to fat-finger a quantity, miss a discount, or attach it to the wrong account.

A web order should become a real Ross sales order automatically, with the customer, the pricing, the tax, and the terms all landing correctly, so nobody's transcribing anything and nobody's introducing typos as a full-time job. The order that took the customer thirty seconds to place should take your team zero minutes to process, because the system did it.

Status has to flow back

The loop closes on the other side: once Ross fulfills and ships, that status — confirmation, tracking — needs to make it back to the store so the customer can see it without emailing to ask. A store that goes silent after checkout trains customers to distrust it. A store that shows them exactly where their order is does the opposite, and it costs nothing once the integration exists.

Shopify or Magento — same discipline, different weight

The two big platforms pull different shops.

Shopify is hosted, API-first, and quick to stand up — you trade some control for a lot of convenience, and its clean APIs make the Ross integration more straightforward. Magento is heavier, self-hosted, and endlessly flexible, which is exactly what some businesses need and exactly what buries the ones who didn't need it — more power, more surface area, more to integrate and maintain. I've built Magento commerce with Stripe payments behind it, so I've felt both the flexibility and the weight firsthand.

Here's the part that matters: the platform choice barely changes the integration discipline. Whichever you run, the same four mappings — products, pricing, inventory, orders — and the same reconciliation underneath decide whether it works. The connector is not the hard part. Keeping two systems honest with each other is.

The B2B wrinkle

One more thing, because a lot of Ross shops aren't pure retail. If you sell B2B, your customers don't see one public price — they see their price, on their terms, against their credit status. That means the store has to respect customer-specific pricing and terms that live in Ross, which is a meaningfully harder integration than a consumer storefront and one that generic e-commerce help routinely gets wrong. It's also where knowing the finance side of Ross — pricing, terms, credit — stops being a nice bonus and starts being the whole job.

The bottom line

If your store and Ross are strangers, your customers are the ones absorbing the awkwardness — in oversells, silence after checkout, and the occasional order that quietly vanished into a spreadsheet. Sync the inventory so you stop selling ghosts, flow orders in without re-keying, push status back so people can see it, and respect B2B pricing if that's your world. Do that and the store finally tells the truth, which — for something customers look at — is worth a great deal.

Re-keying web orders every morning, or apologizing for oversells? Shopify or Magento, that's a fixable disconnect, and the B2B pricing half is exactly where I'm strong. Let's talk →. Related: Ross ↔ CRM.