Adyen EFT POS integration with PetConnect

PetConnect integrates with Adyen EFT POS so card payments happen on a physical terminal while the sale stays inside PetConnect.

Overview and why it matters

When your team works on Adyen EFT POS, the section “Overview and why it matters” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Capture booking numbers, sale references, and screenshots when something looks wrong. Support can usually spot permission or store-context issues quickly when those three items are present.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Prerequisites, roles, and permissions

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Prerequisites, roles, and permissions” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Pro tip: Teams that assign a single “configuration owner” per store roll out changes faster and avoid conflicting edits on busy Mondays.

What Adyen EFT POS means in PetConnect

Front-desk staff experience EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on EFT POS, the section “EFT meaning” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Use fictional test clients while learning. Walk through a booking, a retail sale, and an SMS reply, then remove test data so nobody receives accidental notifications.

Front-desk staff experience EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Capture booking numbers, sale references, and screenshots when something looks wrong. Support can usually spot permission or store-context issues quickly when those three items are present.

Checkout flow on the shop floor

Front-desk staff experience checkout flow under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether checkout flow is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate checkout flow against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on checkout flow, the section “Checkout” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing checkout flow should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Use fictional test clients while learning. Walk through a booking, a retail sale, and an SMS reply, then remove test data so nobody receives accidental notifications.

• Build the basket in PetConnect POS
• Send total to the paired terminal
• Customer completes card authentication on device
• Return approval to PetConnect before handing over goods

Planning before you change anything

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Planning before you change anything” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Use fictional test clients while learning. Walk through a booking, a retail sale, and an SMS reply, then remove test data so nobody receives accidental notifications.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Step-by-step configuration

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Step-by-step configuration” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Use fictional test clients while learning. Walk through a booking, a retail sale, and an SMS reply, then remove test data so nobody receives accidental notifications.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Before you start

When your team works on Adyen EFT POS, the section “before start” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Capture booking numbers, sale references, and screenshots when something looks wrong. Support can usually spot permission or store-context issues quickly when those three items are present.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

After you save

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

Verifying changes with a second staff login

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Verifying changes with a second staff login” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Pro tip: Teams that assign a single “configuration owner” per store roll out changes faster and avoid conflicting edits on busy Mondays.

Day-to-day use on the shop floor

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Day-to-day use on the shop floor” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Use fictional test clients while learning. Walk through a booking, a retail sale, and an SMS reply, then remove test data so nobody receives accidental notifications.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Client-facing impact and communications

When your team works on Adyen EFT POS, the section “Client-facing impact and communications” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Capture booking numbers, sale references, and screenshots when something looks wrong. Support can usually spot permission or store-context issues quickly when those three items are present.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Reporting, reconciliation, and follow-up

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Reporting, reconciliation, and follow-up” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Pro tip: Teams that assign a single “configuration owner” per store roll out changes faster and avoid conflicting edits on busy Mondays.

Integrations with payments, inbox, and retail

When your team works on Adyen EFT POS, the section “Integrations with payments, inbox, and retail” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Capture booking numbers, sale references, and screenshots when something looks wrong. Support can usually spot permission or store-context issues quickly when those three items are present.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Advanced scenarios and multi-store brands

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Advanced scenarios and multi-store brands” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Use fictional test clients while learning. Walk through a booking, a retail sale, and an SMS reply, then remove test data so nobody receives accidental notifications.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Training new hires and seasonal staff

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Training new hires and seasonal staff” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Pro tip: Teams that assign a single “configuration owner” per store roll out changes faster and avoid conflicting edits on busy Mondays.

Troubleshooting checklist

Managers reviewing Adyen EFT POS should treat Hardware Integration documentation as a living playbook. The product receives minor UI improvements regularly, but the sequence—confirm store context, open the correct module, change one thing, verify with a second login—prevents most production surprises. Write internal SOPs in plain language. Link to this Help Center article instead of copying paragraphs into Word—URLs stay current when we improve wording.

Front-desk staff experience Adyen EFT POS under time pressure on Saturdays. A laminated cheat sheet that links to this article reduces questions and stops well-meaning edits to tax or duration fields during a rush. Schedule a five-minute huddle after changes: reception, grooming lead, and retail (if applicable) each confirm their screen looks correct.

Multi-store brands must decide whether Adyen EFT POS is standardised nationally or locally customised. PetConnect supports both, but mixed approaches only work when you document which stores are allowed to diverge. If you integrate Adyen EFT POS, run a live card payment in test mode after changing anything that touches totals, deposits, or checkout.

After a data migration, validate Adyen EFT POS against real appointments and sales for at least one full week before telling clients that everything is settled. Barcode retail teams should scan a known product, a discontinued SKU, and a weighted item (if used) after catalog imports.

When your team works on Adyen EFT POS, the section “Troubleshooting checklist” is where policy meets software. PetConnect is used by grooming salons, daycare centres, and pet retailers that cannot afford to have client records split between a calendar, a till, and a messaging app. Start in the header: the active store location must be correct before you change anything in Hardware Integration. Brand administrators can switch stores; many groomers remain in a single site.

• Confirm the correct store is selected in the header
• Document who approved the change internally
• Test with a fictional client before touching live records
• Refresh the browser after deployments (Ctrl+F5)
• Email support@pet-connect.co if behaviour still looks wrong

Frequently asked questions

Who should read this article?

Owners and managers should read it fully; groomers and retail staff can focus on the sections that match their role. Allow 45–60 minutes if you are configuring production settings for the first time.

Does this apply to every store?

Most settings are per store unless you are signed in as a brand administrator. Confirm the active location in the header before making changes.

Will this change past appointments or sales?

Generally changes apply going forward. Review open appointments and inform clients when pricing, tax, or duration rules change.

Can I print this for training?

Yes. Use your browser print function; the Help Center layout is print-friendly. Update your internal SOP links when article URLs change.

Where can I get account-specific help?

Email support@pet-connect.co with your store name, staff login used, and screenshots of the screen in question.

Summary

Adyen EFT POS is the supported in-person card path; pair terminals per store and train staff on approvals.