do_action( 'mam_wc_make_offer_after' );
do_action( 'mam_wc_accept_offer_after' );
do_action( 'mam_wc_reject_offer_after' );Each fires after the corresponding app request has been processed, immediately before the response is sent:
| Action | Fires after |
|---|---|
mam_wc_make_offer_after |
A buyer’s offer request was handled (a new offer was created, a duplicate was skipped, or — when the requester is the vendor’s own admin — the offer was auto-accepted) |
mam_wc_accept_offer_after |
A seller accepted an offer |
mam_wc_reject_offer_after |
A seller rejected an offer |
No arguments are passed; read the request context ($_REQUEST['id'], $_REQUEST['user_id']) if you need the offer or actor. These are extension points with no consumers in the suite — safe to hook for site-specific side effects.
Example: log accepted offers
add_action( 'mam_wc_accept_offer_after', function () {
$offer_id = absint( $_REQUEST['id'] ?? 0 );
error_log( sprintf( 'Offer %d accepted by user %d', $offer_id, absint( $_REQUEST['user_id'] ?? 0 ) ) );
} );