Theory of operation for Claim Listing — the three-state claim button, the direct-purchase and approval flows, how a claim becomes a native GeoDirectory subscription via the Stripe or In-App Purchase…
The auto-displayed Accept/Decline form a user sees when they have a pending listing-staff invitation — wired through the phone-data hook so it appears on app launch.
Inject a per-staff-member QR code into a left-menu form so venue staff can show it to customers for app-download or scan-to-claim flows.
How mam-geodirectory replaces the static built-in city list in mam-geofilters with cities derived from your actual GeoDirectory listings.
How mam-geodirectory exposes per-listing coordinates, the package’s deal allowance, and ownership-aware tab bar gating to mam-special-offers.
Can't find the answer you're looking for? Don't worry we're here to help!