Index
What is this integration?
The Simec integration connects Golfmanager with Simec machines and readers to interact with your customers through cards or QR codes. The most common uses are:
A reader on the ball machine at the driving range, so the customer pays with a prepaid card or QR.
A reader on turnstiles so members can access certain areas of the club.
A reader on doors to allow access to specific rooms or facilities.
In all cases, the customer presents their QR/card, the machine validates it with Golfmanager and it is deducted from their voucher to dispense balls or allow access.
A voucher is the customer's prepaid balance (for example, of balls or of accesses). The Simec machine reads the customer's QR, asks Golfmanager whether they have balance and, if so, deducts the corresponding amount and acts (dispenses or opens).
What problem does it solve?
Self-service: the customer uses the machine with their QR, without going to reception.
Prepaid with a voucher: each use is deducted from their balance.
Automated access control or dispensing.
Everything recorded: each operation is logged with its result.
How does it work?
The customer presents their QR/card at the Simec machine.
The machine asks Golfmanager (the validation phase) whether that customer has enough balance in their voucher.
If there is balance, the machine performs the operation and confirms to Golfmanager, which deducts the configured amount (and, if applicable, generates a sale).
The machine dispenses the balls or allows access, and the operation is recorded with its result.
ℹ️ The customer is identified by a customer card number (their identifier for Simec), which Golfmanager assigns automatically. That number is what travels in the QR/card the machine reads.
Which systems does it connect and in which direction does the data travel?
It connects the Simec machines with Golfmanager, in real time:
The machine asks Golfmanager (with the QR/customer) whether it can perform the operation.
Golfmanager validates the voucher, deducts and responds, and records the transaction.
For security, the IP address the request comes from must match the one configured for that machine.
Prerequisites (before enabling the integration)
Have Simec machines installed (ball dispensers, turnstiles or door readers).
That each machine is connected to the internet and reachable at an IP address.
Have the Simec module installed, together with the vouchers module.
A voucher type for the balance the machines use, and vouchers loaded for the customers.
Each machine's data (API ID and IP address), provided by the Simec supplier.
Permissions to manage Simec.
Authorization form
To authorize the integration between your company and the system through an API, you normally need to send Golfmanager a document filled in and signed by both parties before you start. Your implementation team will tell you the specific form and how to submit it.
Installing the module
To use this functionality you need to download the module from the App Market. If it is not available to you, contact our support team through the blue bubble in your management software.
Once installed, the Simec configuration and Simec machines options will appear in Settings Menu > System.
How to set it up (step by step)
Step 1 — QR options (Simec configuration)
Settings Menu > System > Simec configuration
Go to Settings Menu > System > Simec configuration.
If your Simec supplier tells you to, enable Reverse QR bytes (depending on the reader type).
If your machines use the Simec dynamic format, enable Dynamic QR format.
Save the changes.
Step 2 — Register the machines (Simec machines)
Settings Menu > System > Simec machines
Go to Settings Menu > System > Simec machines.
Click New.
In the General section, identify the machine: Description (e.g. "Left ball machine"), API ID (e.g. 1, provided by Simec), IP address (e.g.
19.19.215.115:444) and Operation (usually 1).In the Sale section, configure how the transaction is saved: Description (the concept that will appear in the voucher, e.g. "Basket of 30 balls"), Voucher type (where the balance is deducted from, e.g. "Wallet voucher"), Product (optional) and Quantity to deduct (e.g. 1).
Indicate whether the operation Does it generate sales? depending on whether you need a sale or just the voucher deduction.
Save the changes.
With this example configuration, each time the customer takes out balls (if they have balance) 1 unit (€1) will be deducted from their wallet voucher with the concept "Basket of 30 balls".
⚠️ The machine's IP address must match the real one; otherwise the request is rejected. Confirm with the installer/Simec the IP, the API ID and the QR format of each machine.
The configuration fields in detail
Below is an explanation of each field of a Simec machine and of the general configuration.
1) Description (machine)
• Field name: Description
• Description: An identifying name for the physical machine within Golfmanager.
• Impact on the system: It only serves to recognize the machine in the lists; it does not affect the operation.
• Usage example: "Left ball machine".
What happens when it is used: you identify the machine clearly when managing it.
System behavior: it is a descriptive text, with no technical effect.
2) API ID
• Field name: API ID
• Description: A unique identifier for the machine, provided by the Simec supplier. The machine sends it in every request.
• Impact on the system: It lets Golfmanager know which machine is requesting the operation.
• Usage example: 1.
What happens when it is used: Golfmanager locates the machine by its API ID and its operation.
System behavior: if the API ID does not exist, the request is ignored.
3) IP address
• Field name: IP address
• Description: The IP address (and port) where the machine is connected.
• Impact on the system: It is a security measure: Golfmanager checks that the request comes from that IP.
• Usage example: 19.19.215.115:444.
What happens when it is used: only requests coming from that IP are accepted.
System behavior: if the IP does not match, the operation is rejected.
4) Operation
• Field name: Operation
• Description: A number that lets the same machine offer several types of transaction.
• Impact on the system: It distinguishes, for example, "30 balls" (operation 1) from "60 balls" (operation 2), or "spa access" from "gym access".
• Usage example: 1 (the norm if the machine does a single thing).
What happens when it is used: each operation is configured separately (with its voucher/quantity).
System behavior: the machine indicates which operation it requests and Golfmanager applies its configuration.
5) Voucher type
• Field name: Voucher type
• Description: The voucher type the balance is deducted from in that operation.
• Impact on the system: It defines which of the customer's balances each use is subtracted from.
• Usage example: "Wallet voucher" or "Ball voucher".
What happens when it is used: the deduction is applied to that voucher type of the customer.
System behavior: if the customer has no balance in that voucher, the operation is denied.
6) Product (optional)
• Field name: Product
• Description: A product associated with the operation (for example, "Ball basket"). It must be payable with the indicated voucher type.
• Impact on the system: Needed especially if the operation generates a sale.
• Usage example: the product "Basket of 30 balls".
What happens when it is used: the sale (if generated) is recorded with that product.
System behavior: if the product does not accept the voucher, the charge is not done correctly.
7) Quantity
• Field name: Quantity
• Description: The amount or units deducted on each transaction.
• Impact on the system: It determines how much is subtracted from the voucher on each use.
• Usage example: 1 (1 unit / €1).
What happens when it is used: each use deducts that amount from the balance.
System behavior: if the balance is less than the quantity, it is denied.
8) Does it generate sales?
• Field name: Does it generate sales?
• Description: Indicates whether the operation should record a sale or just deduct balance from the voucher.
• Impact on the system: If enabled, in addition to the deduction a sale is created (paid with the voucher); if not, only the balance is deducted.
• Usage example: you enable it if you want each ball basket to appear as a sale.
What happens when it is used: each successful operation leaves an associated sale.
System behavior: if not enabled, the movement only appears as a deduction in the voucher.
9) Reverse QR bytes (general configuration)
• Field name: Reverse QR bytes
• Description: Adjusts the byte order of the QR as required by the Simec reader.
• Impact on the system: It makes the QR be interpreted correctly with certain readers.
• Usage example: you enable it if Simec tells you the reader needs the QR reversed.
What happens when it is used: the QR is validated correctly on those readers.
System behavior: if misconfigured, the QR is not recognized.
10) Dynamic QR format
• Field name: Dynamic QR format (SIMEC)
• Description: Uses Simec's dynamic format (a code followed by date/time) instead of the standard format.
• Impact on the system: It must match the format your machines generate/read.
• Usage example: you enable it if your machines work with the dynamic format.
What happens when it is used: the QR is interpreted with the dynamic format.
System behavior: if it does not match your machines, the QR is not validated.
ℹ️ Note: the exact names may vary slightly depending on your version and language. The function of each field is as described.
Machines and operations
The same physical machine can offer several operations (for example, different quantities of balls, or different accesses). To do this, you register one "machine" per operation, changing the operation number and associating it with the corresponding voucher, product and quantity. This way each operation is configured independently.
If you want the same machine to deduct from different voucher types, you must ask your Simec supplier to enable several operations in the hardware and, in Golfmanager, register one machine per voucher type.
How it is used day to day
The customer presents their QR/card at the machine.
The machine validates and deducts from the voucher, and dispenses balls or gives access.
The movement is reflected in the customer's voucher with the configured concept, and as a sale if the operation generates one.
The customer gets their QR from their voucher / customer area. If your club uses it, there is also a scanner variant to read the QR at reception.
Checking the transactions
In Simec transactions (in the Billing menu) you will see the record of each operation: the machine, whether it was successful or failed, the request and the response, the possible error and the associated sale (if generated). It is the first screen to check when an operation does not complete.
ID/passport scanner (optional)
Simec also offers an ID/passport scanner that connects through a small local service. It is used to auto-fill the customer record (name, surnames, document, date of birth, address…) by scanning the document, speeding up registration at reception. It is configured by indicating the local proxy URL and the service port.
Limitations to keep in mind
The machine's IP must match the configured one, or the operation is rejected.
The customer needs balance in their voucher of the type the machine uses.
Each operation is configured as a separate "machine".
The QR format must match that of your Simec machines.
It depends on the Simec machines and their internet connection.
Frequently asked questions
What is Simec for?
To connect physical machines (ball dispensers, turnstiles, doors) with Golfmanager, so the customer uses them with their QR/card and it is deducted from their voucher.
How is the customer identified?
With a customer card number that Golfmanager assigns automatically; it is what travels in the QR/card the machine reads.
The machine does not operate and gives an IP error.
The IP the request comes from does not match the one configured for that machine. Check the IP address in the machine's configuration and with the installer.
The customer cannot dispense balls or access.
Usually because they have no balance in the voucher of the type the machine uses. The customer must top up their voucher.
The QR is not validated.
The QR format does not match the configuration. Adjust the QR options (Reverse QR bytes or Dynamic QR format) according to your machines.
The product is not charged correctly.
The associated product does not accept the machine's voucher type. Associate a product that can be paid with that voucher.
Can a machine offer several quantities or operations?
Yes. You register one machine per operation (changing the operation number) and associate it with the corresponding voucher, product and quantity.
Does the operation generate a sale or just deduct from the voucher?
It depends on the Does it generate sales? field: if enabled, a sale is created (paid with the voucher); if not, only the balance is deducted.
Where do I check whether an operation was carried out?
In Simec transactions. Each operation shows whether it was successful or failed, and the error detail if there was one.
Does it also work for turnstiles and doors?
Yes. In addition to the ball machine, Simec allows access control on turnstiles and doors: the operation returns an OK/KO to allow or deny passage.
Do I need anything special on the machine?
That it is connected to the internet and reachable at an IP. The data (API ID, IP, QR format) is provided by the Simec supplier.
What is the ID/passport scanner?
A Simec add-on that auto-fills the customer record by scanning their document, to speed up registration at reception.
Who do I contact for machine matters?
The Simec support (see the "Contact and help" section). For the configuration in Golfmanager, our support through the blue bubble.
Recommended best practices
Confirm with the installer/Simec the IP, the API ID and the QR format of each machine.
Create one machine per operation and associate it with the correct voucher and product.
Review the transactions whenever there is an issue.
Inform your customers how to get and use their QR and how to top up their voucher.
Decide "Does it generate sales?" carefully depending on whether you need to record a sale for each use.
Contact and help
For the configuration in Golfmanager or any question, write to us through the blue bubble in your management software.
For the hardware, the installation and the maintenance of the machines, contact Simec support:
Phone: +34 686 93 41 06 (Jesús)
Email: soporte@simec.es