# Adyen in-person supported countries and regions Source: https://help.pet-connect.co/hardware-integration/adyen-in-person-supported-countries-and-regions Before you order terminals or promise card-present payments in a new territory, confirm Adyen in-person support for that country. PetConnect routes EFT/POS payments through Adyen; our integration follows Adyen’s network. ## Why country lists matter for PetConnect + Adyen Managers reviewing Adyen countries 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 countries 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 countries 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 countries 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 countries, the section “Why countries” 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. ## How PetConnect uses Adyen in-person coverage Managers reviewing terminal integration 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 terminal integration 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 terminal integration 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 terminal integration 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 terminal integration, the section “PetConnect Adyen” 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. > PetConnect cannot enable in-person terminals in a country where Adyen does not support point-of-sale acquiring. Online ecommerce availability is a separate Adyen product decision. ## Supported countries and regions (official Adyen list) In-person payments with Adyen (including integrated EFT/POS terminals used by PetConnect) are available in the countries below, grouped by region. Adyen maintains this list; availability can change. Source: Adyen Docs — Locations and languages. Mobile-only Tap to Pay solutions may not support every country listed—verify mobile coverage separately before rollout. ### Americas - Brazil - Canada - Mexico - Puerto Rico - United States of America ### Asia Pacific - Australia - Hong Kong - Japan - Malaysia - New Zealand - Singapore ### Europe - Austria - Belgium - Bulgaria - Croatia - Cyprus - Czech Republic - Denmark - Estonia - Finland - France - Germany - Greece - Hungary - Iceland - Ireland - Italy - Latvia - Liechtenstein - Lithuania - Luxembourg - Malta - Netherlands - Norway - Poland - Portugal - Romania - Slovakia - Slovenia - Spain - Sweden - Switzerland - United Kingdom ### Middle East - United Arab Emirates United Kingdom: includes Guernsey and the Isle of Man. Does not include Jersey and other UK overseas territories and crown dependencies. United Arab Emirates: in-person terminals may not support 5 GHz Wi‑Fi on some Verifone models—plan for 2.4 GHz or ethernet in those sites. ## Using the table in rollout planning Managers reviewing rollout planning 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 rollout planning 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 rollout planning 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 rollout planning 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 rollout planning, the section “Rollout” 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. - Match PetConnect store country and currency to the terminal’s registered country - Order terminals only after your Adyen merchant account is approved for that region - Train staff on decline flows before the first live Saturday with cards ## Mobile, Tap to Pay, and firmware caveats Front-desk staff experience mobile tap to pay 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 mobile tap to pay 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 mobile tap to pay 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 mobile tap to pay, the section “Mobile caveats” 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 mobile tap to pay 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. ## Overview and why it matters When your team works on Adyen regions, 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions, 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. ## Planning before you change anything Front-desk staff experience Adyen regions 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 regions 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 regions 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 regions, 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 regions 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 regions 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 regions 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 regions 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 regions, 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 regions 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 regions, 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions, 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 regions 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 regions 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 regions 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 regions, 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 regions 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 regions, 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions, 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 regions, 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions, 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 regions 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 regions 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 regions 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 regions 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 regions 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 regions, 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 regions 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 regions 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 regions 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 regions 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 regions, 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 Use the formatted country table when planning stores; PetConnect terminals follow Adyen in-person coverage.