Helm Documentation
Product documentation home for Helm client workflows, internal operations, and documentation updates.
Helm is the consignment management and customs workflow surface for Tarifix. It connects customer intake, China warehouse forwarding, item classification, Uganda tax estimation, tracking, document generation, and final handover.
Documentation map
Use the client-facing section for material that can be shared with customers, forwarders, clearing agents, and account stakeholders. Use the internal section for team procedures, review gates, exception handling, and integration behavior.
| Section | Audience | Purpose |
|---|---|---|
| Client docs | Customers, forwarders, clearing agents | Explain what Helm shows, what actions are expected, and how documents and tracking are interpreted. |
| Internal docs | Xtellar logistics, accounts, support, engineering | Standardize operating steps, review gates, and feature behavior. |
| Update workflow | Product and engineering | Keep docs coverage tied to feature work through the feature manifest and CI checks. |
Current feature baseline
The docs are seeded from the current Helm workflow and recent product changes:
- Consignment detail tabs for items, tax estimation, tracking, documents, and customer context.
- Bulk item classification and reclassification from the consignment actions menu.
- Inline editing for consignment items and customer records.
- Separate China and Uganda HS code capture for cross-border handling.
- Cached tax estimates with stale detection when item inputs change.
- Tracking event caching, 17track registration backfill, and domestic shipment status sync.
- 1688 order parsing and translation utilities for better item normalization.
- Supabase cron-based URA currency rate updates.
- GOX shipping invoice generation with Chinese font support.
- AI-estimated tax rate draft review outside the default tax estimate path.
Maintenance principle
Every Helm feature should answer two documentation questions before it merges:
- What does the client or external operator need to understand?
- What does the internal team need to do differently?
The documentation workflow enforces this with a feature manifest and a CI coverage check.