How mrpondi/woocommerce_conduit works
Project type and purpose
– This is a Frappe “app” (a plug-in module for the Frappe/ERPNext framework) named “woocommerce_conduit.”
– Its job is to integrate (synchronize) data between a WooCommerce e-commerce site (external REST API) and a Frappe server (documents/Doctypes, database, web UI, scheduler).
File structure
Top-level:
• configuration files (.editorconfig, .eslintrc, pyproject.toml, modules.txt, patches.txt, hooks.py)
• endpoint.py & woocommerce_api.py (custom API wrappers / whitelisted methods)
• tasks/ (background jobs for syncing orders, items, prices)
• templates/pages/ (HTML/Jinja templates for custom UI pages)
• fixtures/ (JSON fixtures for initial DocType setup)
Sub-package “woocommerce_conduit/woocommerce_conduit” contains:
• doctype/ – JSON metadata, Python controllers, JS scripts, tests for each DocType (woocommerce_server, woocommerce_product, woocommerce_order, logs, settings, shipping rules, etc.)
README for insights
– Installs as a Frappe app via bench CLI.
– Uses Frappe scheduler and background jobs for periodic sync.
– Has pre-commit, GitHub Actions for CI/linting.
– Future plans: webhooks, improved field mapping.