Tracking Refunds
Use HuntBee Tracking Refund for full, partial and repeated OpenCart tracking refunds with safe server-side delivery.
Record full or partial tracking refunds from the OpenCart order page and deliver supported server-side refund events without blocking admin.
Where to find it
Open Sales → Orders → View Order. When Tracking is enabled for the order's store, HuntBee adds a Tracking Refund section to the order page.
What the panel shows
- Original ordered product quantity
- Already refunded quantity
- Remaining refundable quantity
- Partial refund controls
- Full Refund action
- Previous HuntBee refund history
- Provider queue/notices where relevant
Partial refund example
If a product was ordered with quantity 3 and you refund quantity 1, HuntBee records one refund occurrence and leaves quantity 2 refundable. A later legitimate second partial refund receives a different event identity. Reposting the same refund action is protected against creating another occurrence.
Full refund after a partial
A Full Refund uses only what remains refundable. If Product A had quantity 3 and one unit was already refunded, a later full refund records the remaining two—not all three again.
Optional Refunded status mapping
Diagnostics can map one OpenCart order status to an automatic full refund. It is disabled by default. If any HuntBee refund is already recorded for that order, status mapping is skipped and the order-page panel should be used instead.
GA4 refund requirement
GA4 server-side refunds require the original Google Analytics client ID captured when the order was placed. If it is unavailable, the HuntBee refund is still recorded and other eligible providers can still be queued; GA4 is skipped with a clear notice.
Delivery and cron
Refund provider API calls are not made while you wait on the order page. Eligible server events are placed into the Tracking queue and delivered by the scheduler.