Gardners PIM Integration Specialists

iWeb ingests each Gardners SKU and deduplicates by ISBN. You define the family model: one product per ISBN with size/format variants, or separate products per edition (hardback, paperback, audiobook). iWeb routes each variant into your model, flags conflicts and re-routes after updates. You control the family logic; iWeb enforces consistency.

iWeb ingests Gardners' feeds on a schedule you define (daily, multi-day, weekly). Changes are flagged as exceptions if they conflict with your approved product record (e.g. author name change, ISBN correction, out-of-print notice). Merchants review and decide: accept the change, reject it, or create a new product version. iWeb logs the decision and propagates it only if approved.

iWeb maps Gardners' standard fields (title, ISBN, author, publisher, publication date, list price, subject codes, series info) into your PIM schema. You define which are mandatory for publication. You add category mapping, internal SKU, images, promotional copy, channel-specific descriptions and any custom attributes. iWeb enforces completeness rules per channel before publication.

iWeb tracks completeness and approval status in your PIM. A dashboard shows each title's progress: ingested from Gardners, enriched (categories, images, copy added), approved (merchant sign-off) and published (live on channels). Unapproved or incomplete titles are hidden from storefronts until the team signs off.

Yes. iWeb lets you define channel-specific attribute sets (e.g. Shopify Plus sees synopsis + ISBN + price; Amazon sees ASIN + keywords + enhanced description). Same Gardners title, different channel faces. iWeb validates each channel variant against that channel's completeness rules before publication.

iWeb monitors Gardners' availability feed. If a title is marked unavailable or out-of-print, iWeb flags it as an exception and either hides it from the storefront (if configured) or routes it to your team for manual review. You decide: delisting, archiving, or marking as unavailable-for-order. The decision is logged and published atomically across all channels.

You define the refresh schedule (daily, multi-day, weekly, on-demand). iWeb polls or receives Gardners' feed on that schedule, logs the attempt and alerts if it fails (timeout, authentication error, schema change, API downtime). Failed refreshes are logged; your team is notified. New titles do not arrive until the next successful refresh. iWeb does not assume the feed is current - it logs staleness and warns if the feed age exceeds your SLA.

iWeb automates routing: Gardners titles land in your PIM, enrichment and approval workflows flag completeness, and publication routes to all configured storefronts. You do not manually map each title. However, you do decide: which Gardners titles to stock (subscription or filter on publisher, subject, or price range), which attributes are required per channel, and approval gates. iWeb enforces the rules; merchants enrich and approve.

Gardners' list price is ingested as reference. Your pricing strategy (markup, discount, dynamic pricing, customer-specific rates) lives in your ERP or pricing engine. iWeb does not own pricing decisions. The integration ensures Gardners' price is visible to merchants for cost awareness; your system of record (ERP, pricing table, formula) determines what customers see.

Yes. iWeb can filter Gardners' catalogue by publisher, subject, price, availability or custom rules, enrich the subset with channel-specific attributes (ASIN, marketplace keywords, expanded description) and publish only that subset to the target marketplace. You define the filter and channel rules; iWeb enforces them and logs what was published where.

iWeb logs: ingestion timestamp and record count per feed refresh, enrichment and approval milestones per title, publication status and channel, exceptions and resolution. Events flow to your data warehouse for compliance, audit and merchant performance reporting. You can see which titles sold, which enrichment steps took longest, which channels published slowest.

iWeb's mapping and approval history is portable. If you replatform, iWeb re-publishes approved, enriched records to the new storefront using the same attribute mappings (adjusted for the new platform schema if needed). Previously approved enrichment (category, images, copy) does not need re-entry. New channel-specific attributes are configured once and applied. Rollover time is weeks, not months.