Menzzo Partners

Purpose

menzzo-partners handles partner, marketplace, and feed-oriented exports around the Menzzo catalog. It sits near product data distribution, feed generation, and marketplace synchronization.

Stack

• PHP application with Composer dependencies.
• MySQL-oriented data access.
• HTTP integrations through PHP client libraries.
• Feed generation for marketplace and advertising channels.

Connected Projects

• Logidav and Menzzo Magento remain upstream sources for catalog and stock truth.
• Catalog tooling feeds product information into partner export flows.
• Marketplace operations overlap with Logidav marketplace sync runbooks.

Local Docs Submodule

When this repo consumes global docs, use:

cd docs
npm ci
npm start
npm run build

To Expand

• Feed list and ownership.
• Required env vars and credentials.
• Export schedules.
• Failure triage for partner feed rejections.

Dependencies

The page describes partner and marketplace feeds and identifies catalog/stock as upstream concerns. Field-level source ownership and the division of export work with Logidav are not verified here.

Setup

Application setup is not established by this page. Follow the owning repository's README and setup instructions, and request the approved local access or environment you need. The shared documentation submodule and docs-site commands are described in the repository map and local development guide; they do not start this application.

Flows

Stock and catalog is the closest shared flow. Partner export schedules, feed shape, and rejection handling are not source-mapped.

Diagnosis

For a rejected feed, retain the partner response and export timestamp, then identify whether the issue is source data, transformation, or delivery. Feed-specific operational procedures and credentials guidance are missing.

Evidence and gaps

The ChatGPT Ads feed source ownership moved to Logidav; deployment and OpenAI acceptance remain documented separately from the merged source change.

The page has a stack and purpose summary; feed inventory, contracts, schedule ownership, safe setup, credentials handling, and rejection runbooks need verified documentation.

Next evidence to add: source commit and file references for the owned boundary, then repository-specific setup and the relevant operations procedure. See the documentation coverage matrix for the system-wide gap record.