Ready for Commerce vs Plytix

Plytix is built for getting product content out to a lot of places. Their connections page lists dozens of destinations, and all three add-ons on their price list are ways of sending content out: marketplace feeds and templates, brand portals, and printable product sheets. If a retailer wants your whole catalog in their own format by Friday, that is the product built for it.

We're built for the night before that, when your suppliers disagree about the same product. Four of them send you a file. The four files give you four costs, four stock counts and four minimum advertised prices for one cordless drill. Something has to pick a winner for each field, and you have to be able to open that drill in the morning and see which supplier won. That is what our catalog is for, and it is why we connect to five channels rather than fifty.

Both are free to start and neither charges per user.

Everything here about Plytix comes from Plytix's own published pages. Everything about ours comes from our code, read on the date above.

Where your products can end up

If the destination you need is on their list and not on ours, that decides it. Keeping a feed template up to date while a marketplace keeps changing its specification is real work. They do it for dozens of destinations and we do it for none, and nothing below changes that.

Their dozens and our five are counting different things, though. Two Plytix connections install as an app and send your products straight over an API: BigCommerce, whose page calls it "a direct API connection", and Shopify. Those two are also the only channel connectors on their pricing page. Every other destination is a file you upload yourself. Their Amazon page opens with "While Plytix doesn't offer a direct integration with Amazon Seller Central", then goes on to what the feed does instead. Their eBay page carries the same sentence with eBay's name in it. You pick your products, generate the file, and then you're in Seller Central uploading it.

Which of the two you want comes down to how often the catalog changes. A file you upload once a week is fine for a catalog that changes once a week.

What the free plan covers

Both free plans say 500 and it isn't the same 500. Sell one shoe in six colours and ten sizes and you have sixty things a customer can buy. Plytix counts that exact shoe four different ways in their own documentation, and depending on how you set the parent product up it lands on "60 SKUs in total" or "70 SKUs in total". So seven of those shoes fill a Plytix free plan, and whether the eighth fits depends on how you set the products up months ago. Here those seven shoes are seven products. A variant belongs to a product rather than sitting beside it as a row of its own, so 500 stays 500 whatever sizes you stock.

The other row worth reading twice is how you open an account in the first place. A Plytix account goes through their team, and their own page is direct about it. It says "Book a quick call with our team". On how you get a free one: "Everyone begins on a free plan after the intro or demo call." Ours opens when you register, with no card and no call. The first channel you connect brings your existing listings in with it.

What it costs once you outgrow the free plan

Plytix's free tier is more generous than a lot of products' paid ones, and their own plan grid marks only four things as missing from it. You go without user roles, advanced user permissions, single sign-on and automatic inheritance, all four of which start at Pro. You keep 500 SKUs, unlimited seats, 50 GB of storage, scheduled imports, exports, webhooks, product families, workflows and 500 AI credits a month. Support is live chat and email until you're paying, then an assigned manager.

Then you cross 500 SKUs, and between 0 and 499 there is nothing. Six hundred SKUs or fifty thousand, it's the same $499 a month. Ours starts at $49 for up to 1,500 products, then $99, $179 and $319, on a slider you move yourself on the pricing page.

Add-ons are the other half of a Plytix bill, and they're monthly rather than one-off. The marketplace feeds and templates that reach those dozens of destinations cost $300 a month, brand portals $300 and product data sheets $200. Their Shopify and BigCommerce apps are add-ons priced at zero. Onboarding is the one-off part, free at the standard level and $3,000 for the tier their page says 82% of customers pick.

Every one of our plans includes every feature, so our free plan is the same software as our most expensive one. You get the five team roles, the supplier feeds and every rule below them, thirty days of history and the channel connections, whether you're paying or not. Cross 500 products and you're paying for more products, never for more software.

Their single price works out cheaper once the catalog is big enough, and it's worth knowing where that happens. Twelve thousand products with no variants is $319 a month here against $499 there. Cross twelve thousand and ours steps to $549 while theirs stays at $499, and theirs stays cheaper from there upwards. Variants swing it back the other way, since two thousand products in five sizes and two colours is still 2,000 products here at $99 a month, and around 20,000 SKUs there at $499.

What happens to a product before it goes out

Seven days is the row to measure against your own week. A supplier feed that went wrong on a Friday and got spotted the following Wednesday is already past it. Plytix's documentation covers opening a past version, sorting the list and exporting the changes to CSV, and restoring one isn't among them. Ours keeps thirty days on every plan, and a product that's still live keeps its latest version forever, so you always have something to go back to.

⚠ "Not documented" means exactly that, and not "no". We read our side in our code and theirs on their published pages, so where their pages don't cover something we say so rather than claim it can't be done.

What a connection is made of

Connecting a channel here starts by reading rather than writing. You authorise it once, and the first sync pulls everything in. We read your online store or your point of sale, and what's there becomes products in the catalog. Amazon matches your existing listings by seller SKU and writes down the ASIN of each one. From then on the catalog is the one in charge, and every publish overwrites every field on the channel, which also means a title you edit in Shopify is gone again the next time we publish.

The day something fails, the message tells you which of two things happened. When we sent it and the channel refused, it names the field and hands you the channel's own words. When we stopped it before we ever sent it, it says so instead. The message reads: "This product wasn't sent to Amazon because it has no price." A spreadsheet row that failed on upload gives you neither, because a file has nowhere to answer from.

Five is where we are today. The rest of the list is already on the integrations screen, marked Coming soon.

When two suppliers disagree about the same product

Three suppliers carry the same cordless drill. The first is the one you actually buy from and writes the best descriptions. The second is two dollars cheaper. The third is the only one who ever has it in stock. Every night all three send you a file, and every file has an opinion about the cost, the minimum advertised price and how many are on the shelf. If nothing decides, the feed that finished last wins, which means your prices are set by whichever supplier's server was slowest.

You pick a rule for each field, and there are three of them. Each one is spelled out on screen while you're choosing.

• –"Drag-reorder sources. The first source in your list with a value for this field is selected."
• –"Pick the source whose chosen decider field has the lowest numeric value."
• –"Pick the source whose chosen decider field has the highest numeric value."

So the description comes from your usual supplier because you put them first, the cost from whoever is cheapest and the stock from whoever has the most. All three decide on the same drill on the same night. Fields that belong together can be grouped, so a cost and the stock behind it come from one supplier instead of coming from two different ones.

That first rule didn't always say "with a value". A supplier used to win a field just by having a row in the feed. So your best supplier could send an empty cell, take the field anyway, and drop a blank on top of the price you already had. The supplier further down the list, the one with the real number, was never asked.

A rule can have a condition on it too, and the obvious one is "use this supplier's cost only while they have stock". On a night when no supplier passes that condition, nothing is taken and the value you already had stays where it is. A condition is you saying what you're willing to publish.

Quantities are the one exception. A rule that says "cheapest supplier with stock above zero" stops matching anybody the moment a supplier sells out. Keeping the last number would leave you advertising stock nobody has, so when every supplier the rule skipped said zero, zero is what gets written.

Feeds keep products up to date and they don't create them. A row matching nothing in your catalog is logged as unmatched and stops there, so you add a supplier's new products yourself, once, and the feed takes them from there.

Why one supplier won

Open the drill and every source with a record for it gets a row, including the ones that had nothing to offer. Those empty rows are the point. When the rule follows the order you set, the winner only makes sense next to the suppliers that were asked and came up empty. Hiding them would hide the reason. The winner gets a "Selected" badge, and when the rule couldn't pick anybody, the row says so in the product's own words: "The rule couldn't pick a source, so the most recently updated one is selected."

There are two dates on that screen, and the help text is there because people read them as one. Last run "is the last time this data source checked its source" while last updated "is the last time this value actually changed". One supplier is still sending you a file every night and hasn't moved a price since March. Another stopped sending anything at all. A single date can't tell those apart, and they need two completely different phone calls.

Where Plytix is ahead

Reach. Dozens of destination templates they keep up to date, plus retailer templates and InDesign, against our five connections. If the place you need is on their list and not on ours, they get your data there today and we don't.

Approval before something goes out. Workflows are on every Plytix plan including the free one, with the review and sign-off steps you set up. Ours has no approval step today. Changes land in the catalog as they're made, every one of them is kept in a version history, and nothing waits for a second person to say yes.

Content that differs by language. Their Shopify content manager translates and localises across markets. We're building the same thing and it isn't ready, so a catalog that has to ship in Spanish and German is theirs today.

Catalog PDFs and brand portals. Automatic product sheets and a portal your buyers can browse are add-ons on their side and don't exist on ours.

Three more are worth knowing before you start rather than after. Their AI writes text and generates images on every plan, the free one included, while ours edits photographs and doesn't write product copy yet. Their API is documented and both reads and writes, and ours isn't out yet, so for now everything happens in the interface. And single sign-on, along with permissions more detailed than a role, starts at their Pro tier and doesn't exist on ours.

Which one to choose

Plytix, if the destination you need is on their list and not on ours, or if a feed template somebody keeps up to date is what you were looking for in the first place. Also if somebody has to approve product copy before it goes out, or if you need that copy in more than one language. Same if your buyers need a portal or a PDF, or if you're going to build on an API. And above about twelve thousand products with no variants, their single price is cheaper than ours and stays cheaper.

Ready for Commerce, if the difficult part happens before anything is published.

• –Several suppliers cover the same products and you want one rule per field deciding who wins.
• –You want to open a product and see which sources were asked and which one was taken.
• –Your catalog has variants and you'd rather not be billed for each one.
• –You're somewhere between 500 and twelve thousand products, where their ladder has one step and ours has five.
• –You want to register this afternoon and see your own store's products on screen before you've spoken to anybody.

Some catalogs have to say different things on different surfaces: a short description for the mobile app, a longer one for the print catalogue. That is a third kind of system, and it belongs to the enterprise tools. Our comparison with Akeneo covers what that buys and what it costs. And if you're earlier than any of this and still working out what the category does, what a PIM actually is is the ground under all three.

Our prices sit on the pricing page. The catalog is free to 500 products and starts at $49 a month above that, with every feature on every plan whatever you pay. Plytix publishes Standard at zero up to 500 SKUs and Pro at $499 a month up to 50,000, with the add-ons priced separately. Ours needs no call to start, so the shortest way to settle it is to register, connect your store and see your own products on screen this afternoon. Getting a catalog out of spreadsheets covers a first day on ours, and says plainly what doesn't come across.