action
-
Hook: mam_wc_pv_process_vendor_registration
Action that creates a vendor for an existing user: inserts the wcpv_product_vendors term, copies billing meta, geocodes the address, sets the user’s role, and emails the site admin. The hook…
-
Actions: mam_wc_make_offer_after, mam_wc_accept_offer_after, mam_wc_reject_offer_after
Lifecycle actions fired after an offer is created, accepted, or rejected through the app — extension points for custom side effects like CRM syncs, analytics, or extra notifications.
-
Hook: mam_ride_share_driver_update
The driver home-screen button action: toggles the driver’s punch state when idle, and walks an active assignment through the en-route → pickup → destination → completed trip stages with GPS…
-
Hooks: mam_wc_delivery_request_driver, mam_wc_delivery_start_order, mam_wc_delivery_no_driver_accepted
The external-driver dispatch filter (the DoorDash hand-off point) and the two cron task hooks: order-due-to-start vendor reminders and no-driver-accepted admin alerts.
-
Hooks: mam_check_in and mam_wc_pv_complete_order_check_in
The two actions that advance an order along its transport-status ladder: the app’s check-in button and the Product Vendors complete action. What a single advance does, the request contract, and…
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
