HFT71 Plugin Documentation
Operational documentation for deploying and maintaining the HFT71 Integration WooCommerce plugin (v1.3.0).
Admin menu (since v1.3.0)
The plugin uses a top-level HFT71 menu in wp-admin (not under WooCommerce):
| Submenu | Purpose |
|---|---|
| Ustawienia | API credentials, sync intervals, status mapping, feature flags |
| Logi | API request/response log (hft71_api_log table) |
| Modele | Product model configuration (SKUs, sizes, prices) |
| Kolory | Shared color palette used by models |
Documentation
| Document | Description |
|---|---|
| Release checklist | Pre-production deployment checklist |
| Runbook | Incident handling (API outage, webhooks, stock drift) |
| Operations checklist | Daily and weekly maintenance tasks |
| API examples | Request/response examples for integration flows |
| JSON schemas | Payload and configuration schemas |
Product model configuration (v1.3.0)
Centralized model data is stored in custom DB tables (hft71_models, hft71_colors, hft71_model_colors, hft71_model_skus).
- One-time seeder imports palette, models, SKUs, descriptions, and prices from theme runtime data on first activation.
- Admin CRUD via HFT71 > Modele and HFT71 > Kolory.
- Public read helpers:
hft71_get_models(),hft71_get_model(),hft71_get_model_sku_map(), and related functions (each filterable). - Normalized config shape:
schemas/model-config.schema.json. hft71_model_price_changedaction fires when base price or double-sided surcharge changes.
Shipping sync (v1.1.0)
- One-way sync from HFT71 to WooCommerce for
shipping.carrier,shipping.tracking, andshipping.trackingRet. - Triggered by cron poll, selected order events, and manual admin action in the order meta box.
- Feature-flagged by
hft71_shipping_sync_enabled. - Verify via order meta
_hft71_shipping_*, log actionssync_shipping/sync_shipping_skipped, and the order meta box section.