Index
What is this integration?
The The Bucket Pro integration connects Golfmanager with the ball dispensing service Bucket Pro.
When a customer pays for a ball product, the system automatically generates the Bucket Pro codes and prints them as a QR code on the receipt. The customer uses that code at the dispenser to collect their balls.
The Bucket Pro is the system that controls the ball machines. This integration turns each ball purchase into a code (QR) valid for the dispenser, without tokens or manual handling.
What problem does it solve?
Sale and dispensing in a single step: on payment, the customer already receives their ball code.
No physical tokens: the code is printed on the receipt.
Automatic: there is no need to generate the code by hand.
Everything is recorded on the sale.
How does it work?
The customer buys a ball product marked as Bucket Pro.
On paying the sale, Golfmanager asks Bucket Pro for one code per unit sold.
The codes are saved on the sale and printed as a code/QR on the receipt (physical and virtual).
The customer uses the code at the dispenser to collect the balls.
If the sale is cancelled, the Bucket Pro codes are removed from it.
Which systems does it connect and in which direction does the data flow?
It connects the Golfmanager POS with the Bucket Pro service:
On payment, Golfmanager asks Bucket Pro for the codes.
Bucket Pro returns the codes, which Golfmanager saves and prints.
The ball dispensing is handled by Bucket Pro when it reads the code.
Prerequisites (before activating the integration)
Have a Bucket Pro account with access to its API.
Have the The Bucket Pro module installed, together with the POS and billing modules.
Your Bucket Pro data: API URL, API Key and your site identifier (Site ID).
Administration (billing) permissions to configure.
How to set it up (step by step)
Step 1 — Connection data
Log in to Golfmanager with a user that has billing permission.
Go to Bucket Pro > Settings.
Enter the API URL, the API Key (stored encrypted) and the Site ID that Bucket Pro provides.
Save the changes.
Step 2 — Ball products
Go to the record of each ball product.
Check the "Bucket Pro product" box.
Indicate the ball count that purchase includes.
Save the changes.
⚠️ Every product marked as Bucket Pro must have its ball count. If it is missing, when you save the product or sell it the system will show an error. Start with the test (sandbox) credentials and switch to the real ones when everything works.
Explanation of each field
Below is a description of each field in the integration: where it is, what it means, its impact on the system, and a usage example (what happens when it is used and how the system behaves).
A) Connection data (Bucket Pro > Settings)
1. API URL
Description: the address of the Bucket Pro service the codes are requested from.
Impact on the system: essential. It indicates which environment (test or live) it connects to.
Usage example: you enter the sandbox URL to test and the real one when going to production.
What happens when it is used: Golfmanager calls that URL on payment to generate the codes.
System behavior: if it is missing, "Bucket Pro: the API URL is not configured" appears and no codes are generated.
2. API Key
Description: the credential that authorizes the connection with Bucket Pro. It is stored encrypted.
Impact on the system: essential to authenticate.
Usage example: you copy the key Bucket Pro provides.
What happens when it is used: each code request is authenticated with it.
System behavior: if it is missing, "Bucket Pro: the API Key is not configured" appears.
3. Site ID
Description: the identifier of your site/club in Bucket Pro.
Impact on the system: essential. It indicates which installation the codes belong to.
Usage example: you enter the Site ID Bucket Pro gives you.
What happens when it is used: the codes are generated for your site.
System behavior: if it is missing, "Bucket Pro: the Site ID is not configured" appears.
B) On the product
4. Bucket Pro product (checkbox)
Description: marks the product as a ball product managed by Bucket Pro.
Impact on the system: only marked products generate a code when paid.
Usage example: you check it on your "Bucket of balls" product.
What happens when it is used: when that product is charged, the ball code is generated.
System behavior: a product without this mark does not generate any code.
5. Ball count
Description: how many balls that purchase includes (the bucket size).
Impact on the system: it is mandatory on Bucket Pro products; it is the number of balls sent to Bucket Pro.
Usage example: on a 50-ball bucket you set 50.
What happens when it is used: the generated code entitles to that quantity of balls at the dispenser.
System behavior: if it is marked as Bucket Pro but without a ball count, "The product requires a Bucket Pro ball count" appears (when saving the product or selling).
C) On the sale
Bucket Pro code: the code (or codes) generated for that sale. Impact: it is what is printed on the receipt and used by the customer. Behavior: it is read-only; if the sale has several units, the codes are shown separated by semicolons.
Bucket Pro status: indicates the result of the generation. Impact: it helps to know whether the codes were created. Behavior: it changes to "Processed" when the codes have been generated; "No ball lines" if the sale has no ball products.
How to use it day to day
Sell the ball product at the POS like any other.
On charging, the Bucket Pro code (QR) appears on the receipt (printed or on the virtual receipt/popup).
The customer uses the code at the dispenser for their balls.
On the sale record you can see the "Bucket Pro code" field (the generated codes) and the "Bucket Pro status" field, which changes to "Processed" when the codes have been generated. If a sale includes several units, the codes are shown separated by semicolons.
Limitations to keep in mind
Each Bucket Pro product needs its ball count; without it, the sale errors.
The codes are generated on payment: an unpaid sale does not have a code yet.
One code is generated per unit sold; several units, several codes (separated by semicolons).
If the sale is cancelled, the codes are removed from the sale.
It is one-way (Golfmanager asks; Bucket Pro responds) and is triggered on payment.
It depends on the Bucket Pro service: if its API is unavailable, the codes are not generated at that moment.
Frequently asked questions
When selling (or saving) a ball product I get an error.
Usually the product is marked as Bucket Pro but has no ball count; "The product requires a Bucket Pro ball count" appears. Indicate the ball count on the product record.
The code is not generated on payment.
Review the connection data: if any is missing, notices like "Bucket Pro: the API URL / the API Key / the Site ID is not configured" appear. Complete the API URL, the key and the Site ID, and try again.
"The response did not contain a code" appears.
Bucket Pro did not return a valid code (service unavailable or unexpected response). Check that the Bucket Pro service is operational and that the credentials are correct, and retry the charge.
The code does not appear on the receipt.
The code is generated on payment. If the sale is not yet charged, there is no code yet. Charge the sale and the code will appear on the receipt (physical and virtual).
The dispenser does not accept the code.
Check the status of the sale and the code on its record (the "Bucket Pro code" and "Bucket Pro status" fields). If the sale was cancelled, the code was removed.
The customer bought several buckets. Do they get one code or several?
One per unit. If they buy 3 buckets, 3 codes are generated, saved together (separated by semicolons) and all printed on the receipt.
What identifies the customer at the dispenser?
The code itself, printed on the receipt. No card or membership number is needed: the customer enters or scans that code at the machine.
How do I set up different bucket sizes?
Create a product for each size (for example, 30, 50 or 100 balls), mark each as Bucket Pro and indicate its ball count.
Where do I review a sale's codes?
On the sale record: the "Bucket Pro code" field shows the codes and "Bucket Pro status" indicates whether they are "Processed".
How do I test before operating for real?
First configure the test (sandbox) credentials that Bucket Pro provides and make a test sale; switch to the real credentials when everything works.
Is the code refunded if I return the sale?
When the sale is cancelled, the codes are removed from the sale in Golfmanager. Managing the dispensing (if the customer already collected the balls) is up to Bucket Pro.
Recommended best practices
Configure the ball count on all Bucket Pro products.
Test first with the sandbox credentials before operating for real.
Check that the code appears on the receipt (physical and virtual) after charging.
On a problem, review the sale record (Bucket Pro code and status).