Customer and pet profiles in depth

This guide covers Customer and pet profiles in depth in the Features section of the PetConnect Help Center. It is written for pet grooming salons, daycare centres, and pet retailers worldwide using appointments, retail, and client messaging on one platform. Plan 45–75 minutes to read and complete the exercises in a test store before changing live settings.

Overview and why it matters

When your team works on Customer and pet profiles in depth, 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth, 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth, 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. 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 Customer and pet profiles in depth, 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. Brand administrators can switch stores; many groomers remain in a single site.

Managers reviewing Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. 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 Customer and pet profiles in depth should treat Features 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth 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 Customer and pet profiles in depth, 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 Features. 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

You should now understand how Customer and pet profiles in depth fits into PetConnect’s Features workflows. Bookmark this page and revisit it when you hire, open a new location, change pricing, or refresh hardware.