Problem
, Manual catalog ops could not scale
Reviewing thousands of retail SKUs by hand, applying ingredient policies, and pushing them to Shopify was slow and error-prone. Chain-level stock/price data had to stay aligned with the store catalog, and non-compliant products could not remain live.
Solution
, End-to-end operations panel
Secure Shopify OAuth; Kroger API catalog search by chain/location; Purely Filter Engine scoring (FOOD / BABY / PET / CLEANING) with ACCEPTED–REJECTED–REVIEW; single and bulk Shopify import; UPC matching; background scan/delete workers and Excel reports.
Technical Architecture
, Flask, workers, local DB
Flask app factory with auth, products, collections, brands, integrations, filter, and purely blueprints. Shopify Admin API wrapper; Kroger client (auth, products, locations, bulk import, mapper); Filter Engine (Excel rules → JSON cache); job/progress UI for long scans; SQLite for import and match records.
Outcomes
, Faster, more consistent catalog Sub (EN) Operational gains
Ingredient policy is enforced in code; dry-run scans followed by targeted deletes; chain dashboards and matching screens; storefront nav sync plus store-first validation/cleanup centralized Purely store operations.