Your Google Shopping feed is a URL now. It updates itself.

In Apimio you build the feed from your catalog rather than exporting a file. Choose the Google Shopping template, select which products belong in it, map your categories to Google's taxonomy, set a refresh schedule, run the pre-publish check, and Apimio hosts the feed at a stable URL (Advanced and Enterprise plans). You paste that URL into Google Merchant Center once as a scheduled fetch. Merchant Center then polls it on its own schedule and always finds current data, so there is no export to repeat and no upload to forget.

Most disapprovals trace back to the product data rather than the feed file — a missing GTIN or MPN, a title over the limit, an availability value Google does not accept, an image under minimum size, a price in the feed that no longer matches the landing page. That is why Apimio scores products against 74 quality rules before they are eligible for a feed and then runs the pre-publish diagnostics on the feed itself, listing every product that would fail with a click-through to fix it. Connect Merchant Center and the real rejection status comes back next to the prediction, so fixing the data upstream removes the cause instead of resubmitting the symptom.

No, and it is worth being exact about this. Apimio generates hosted feed files and URLs that those channels read on their own schedule, plus marketplace-formatted TSV files for Amazon and Walmart that you upload. That is not a live API connection. Shopify is the only channel Apimio syncs with live and two-way. Separately, you can connect your Merchant Center or Commerce Manager account so Apimio pulls item-level rejection status back — that is a read of the channel's verdict, not a push of your products.

A feed app solves transport: it takes the data you already have and ships it to a channel in the right shape. It has no view on whether that data is complete, so incomplete products become disapproved products. Apimio scores and fixes the data first, predicts the rejections, and then feeds it, from the same catalog that syncs to your stores. Honest limit: if your product data is already clean and a feed is genuinely all you need, a dedicated feed app is cheaper. Apimio wins when data quality is part of the problem. The longer comparison is at /product-feed-management.

Yes. Each feed carries its own product selection, filtered by collection, vendor, tag, attribute value or quality score, and its own refresh cadence. You can put your full range on Google Shopping, a curated subset on Meta and only Channel-Ready products on TikTok without maintaining two catalogs or two exports. Apimio supports up to 25 hosted feeds per organization (Advanced and Enterprise plans).

No. Wholesale price, MOQ, case pack and lead time are a separate internal attribute class in Apimio, not ordinary product fields. They are excluded from every feed, every Shopify sync path and every public surface by construction — not by a setting somebody could switch off by accident.

It maps your categories to Google's taxonomy; it does not AI-guess a category for each product. You map each of your own categories to a google_product_category value once, and every feed template that requires the field — Google, Meta, Pinterest, TikTok, Bing — reads the same mapping. That is what stops the “invalid product category” rejections those channels return for free text. Apimio AI can suggest a product type for products whose category field is empty, and you review those suggestions before they save, so you stay in control of how products are classified.

A capped set of the rules that actually cause rejections, not the entire channel specification: required fields for that channel and product type, title length, availability values against the accepted vocabulary, image minimum dimensions, price and currency consistency between feed and product, and GTIN presence. Each finding is a clickable row that opens the product so you fix it in the catalog rather than in the file, and a stale-feed badge shows when a feed has not refreshed on schedule. Apimio then pulls the channel's real verdict back after processing, so anything the check does not cover still surfaces on the product.

Yes. TikTok product feeds and Pinterest catalogs are templates on the same engine as Google Shopping, Meta and Bing (Advanced and Enterprise plans), generated from the same canonical record and the same Google taxonomy map that both channels require for the product category. Each gets its own hosted URL, product selection and refresh cadence. Give the channel the URL as a scheduled fetch and the feed stays current on its own; a title or price fix in Apimio reaches TikTok, Pinterest and every other channel at the next refresh.

A feed shaped for an LLM or AI shopping assistant to read rather than for an advertising channel to import: complete attributes, resolved categories, plain-language descriptions and none of the channel-specific fields. Apimio generates it as a template on the same feed engine and serves it as a hosted URL (Advanced and Enterprise plans). It can be mapped to what the ChatGPT and OpenAI product-feed programs ask for; it is not an official OpenAI specification. The full explanation is at /chatgpt-product-feed.

Advanced PIM at $399 a month and Enterprise PIM from $999 a month. Product Feeds are not part of Basic PIM at $199 a month — along with Scheduled Imports, Sale Scheduler, the Image Library, multi-language and the public API, they sit on Advanced and above. Basic PIM includes the catalog, Quality Guard, Bulk Edit, Line Sheets and the AI content assists. Apimio offers a 14-day free trial, and if a subscription lapses your feeds pause rather than delete.

Pinterest reads a product catalog feed, so the connection has two halves. In Pinterest Business you claim your domain, open Catalogs and add a data source by pasting a feed URL, then pick the country and language. The other half is producing that feed: Apimio generates a Pinterest catalog feed from your Shopify catalog at a stable hosted URL, with the required fields and a category drawn from Google's product taxonomy, and refreshes it on the cadence you set (Advanced and Enterprise plans). Apimio does not sign in to Pinterest or run Pinterest ads — the account connection is made in Pinterest's own manager.

The shop itself is TikTok's side of the job: you register a seller account in TikTok Seller Center, get approved, and manage listings, inventory and orders there. What Apimio contributes is the product data — a TikTok product feed generated from your Shopify catalog at a hosted URL, with TikTok's required fields mapped from the canonical record and a category from Google's product taxonomy (Advanced and Enterprise plans). Pre-publish diagnostics flag missing fields, overlong titles and undersized images before TikTok rejects them. Apimio does not create the seller account or handle orders.

Yes. Pinterest is one of the channel templates on the same feed engine as Google Shopping, Meta, TikTok and Bing, so it is generated from the same product records and the same category map (Advanced and Enterprise plans). The feed lives at a stable, tenant-scoped URL that Pinterest polls, carries its own product selection and refresh cadence, and excludes wholesale and internal fields by architecture. Apimio produces the feed the channel reads; adding it as a data source, and anything else inside Pinterest, happens in Pinterest Business.