Skip to main content
Bear SoftwareACP Feed Optimizer

Case studies

Operational case study structures, ready for verified publication.

These pages are built as public-safe case study templates. The workflow detail is real, but any merchant name, quote, logo, or measured result still requires written approval and verification before publication.

Case Study Template 01

Verification pending

Disapproval recovery workflow for a Shopify catalog with identifier and title issues

Publication-ready structure for a merchant case study focused on missing GTINs, weak titles, and feed approval blockers. Merchant details and measured results are still awaiting approval.

Company snapshot

  • Merchant name pending written approval before publication.
  • Current placeholder scope: Shopify home and living catalog using Google Shopping and Meta.
  • Catalog operations and paid media both depended on the same product feed.

Initial feed problem

The merchant had a growing set of feed blockers across high-priority products, including missing identifiers, weak product titles, and inconsistent variant data.

Why it mattered commercially

Those issues can reduce approvals, suppress product visibility, and force the team into manual cleanup instead of campaign and merchandising work.

What ACP found in the audit

  • Critical products with missing GTIN, brand, or other identifier coverage gaps.
  • Titles that did not carry enough product context for clean channel matching.
  • Variant and attribute issues that made feed quality harder to maintain as the catalog changed.

What fixes were prioritized

  • Repair missing identifiers on the products most exposed to paid channels.
  • Rewrite weak titles on products with high feed visibility risk.
  • Normalize variant and attribute data before the next sync cycle.

What changed operationally

  • Move from ad hoc spreadsheet triage to one prioritized issue queue.
  • Give catalog and performance teams the same audit language for severity and product impact.
  • Use a review-first workflow before any catalog changes are published.

Results

Disapproval reduction

TODO: add verified before and after disapproval count.

Use Merchant Center or channel export data with dates.

CTR improvement

TODO: add verified CTR change for the audited product set.

Cite the reporting window and traffic source.

ROAS improvement

TODO: add verified ROAS change only if attribution is defensible.

Separate feed cleanup impact from bidding, budget, and creative changes.

Variant error reduction

TODO: add verified reduction in variant-related feed errors.

Use the same rule set before and after cleanup.

Time saved

TODO: add verified workflow time saved per week or month.

Document who measured it and what tasks were removed.

Quote slot

TODO: add an approved merchant quote with name, role, and publication consent.

Open full template

Case Study Template 02

Verification pending

Variant normalization workflow for a Shopify catalog with inconsistent size and color data

Publication-ready structure for a merchant case study focused on broken variant grouping, attribute inconsistency, and cleanup prioritization. Merchant details and measured results are still awaiting approval.

Company snapshot

  • Merchant name pending written approval before publication.
  • Current placeholder scope: Shopify apparel or accessories catalog with large variant depth.
  • Multiple channels depended on consistent color, size, and parent-child variant structure.

Initial feed problem

The catalog used inconsistent option values and incomplete attributes, which made related products hard to group cleanly across shopping and social channels.

Why it mattered commercially

When variants are messy, channels can split product groups, dilute listing quality, and create more manual catalog cleanup for the merchant or agency managing the account.

What ACP found in the audit

  • Color and size values were not standardized across related products.
  • Variant structure and attribute gaps were reducing downstream feed consistency.
  • Product-level recommendations were needed to decide which items to normalize first.

What fixes were prioritized

  • Normalize shared variant values for color, size, and related options.
  • Repair attribute coverage on the products with the highest channel exposure.
  • Review before and after product previews before pushing updates live.

What changed operationally

  • Create one naming standard for high-volume variant fields.
  • Reduce repeated manual cleanup by documenting issue patterns inside the audit workflow.
  • Use the same audit output for merchant review and agency reporting.

Results

Disapproval reduction

TODO: add verified before and after disapproval count.

Use Merchant Center or channel export data with dates.

CTR improvement

TODO: add verified CTR change for the audited product set.

Cite the reporting window and traffic source.

ROAS improvement

TODO: add verified ROAS change only if attribution is defensible.

Separate feed cleanup impact from bidding, budget, and creative changes.

Variant error reduction

TODO: add verified reduction in variant-related feed errors.

Use the same rule set before and after cleanup.

Time saved

TODO: add verified workflow time saved per week or month.

Document who measured it and what tasks were removed.

Quote slot

TODO: add an approved merchant or agency quote with publication consent.

Open full template