Overview
Project sync on the La Marie Beauty Bookly-Square integration. Three issues were on the table: a blocked card-capture flow for $0 services (the project's core requirement), a product location bug in Square suspected to be caused by a lingering Zapier integration, and a resolved "new line" character bug. Kimberly was sick and cameras-off; Eshock (Isahaque) was not present but had shared findings via Slack prior to the call.
Attendees:
- Kimberly Gehrmann (external — lead investigator)
- Melissa Cusumano (Asymmetric)
- Mark Hope (Asymmetric)
- Roxana Lopez (La Marie Beauty)
- Katie Schueller (La Marie Beauty)
- Lisa Frommelt (La Marie Beauty)
- Isahaque "Eshock" Mahmud (Asymmetric — not present)
- Chris Ostergaard (Asymmetric)
Key Decisions
- Kimberly will own the Bookly investigation this weekend. The team agreed the issue is complex enough to require a dedicated deep-dive into Bookly's documentation before any further development work. The question on the table: is Bookly the right plugin at all, or does it need to be replaced?
- Eshock's code is not the root cause of the card-capture failure. His investigation concluded the problem lies with Square's API behavior for $0 transactions, not the custom integration code.
- Bookly page route changed from
/servicesto/appointments. Eshock made this change; the/servicespage is now correctly displaying service tiles again.
Issues
🔴 Bookly–Square $0 Card Capture — BLOCKED
The core project requirement is to capture a credit card on file during a $0 service booking (pre-appointment authorization). This flow is currently broken.
- A test booking completes successfully end-to-end in Bookly.
- Card data does not appear in the Square dashboard after booking.
- Melissa independently confirmed this behavior during testing earlier in the week.
- Eshock spent significant time investigating and coding the checkout flow; his conclusion is that the issue is with Square's API, not the custom code.
- The team is running against the live Square environment — no staging Square instance exists.
Path forward: Kimberly will research Bookly's documentation over the weekend to confirm whether the plugin supports the $0 service + card-capture workflow natively, and to assess whether Bookly should be replaced. She will review the Loom walkthrough and Miro board Melissa provided for context.
🟡 Product Location Bug — Zapier Suspected
Approximately 12 products in Square had their location switched unexpectedly. This is not the first occurrence — a similar incident happened early in the project when Zapier was first connected.
- Square support identified Zapier as the only possible cause of the location switch.
- The team believed Zapier had been fully disabled when Chris transitioned off the project, but this has not been confirmed.
- Roxana noted the original Square support email detailing the affected products was not attached when forwarded to Melissa.
Path forward:
- Melissa will audit all Zapier accounts associated with the project to confirm no active integrations remain.
- Roxana will forward the original Square support email (from Lisa's inbox) detailing the affected products.
✅ "New Line" Character Bug — RESOLVED
A bug was causing a literal \n (slash + newline) to appear in rendered text on the site.
- Root cause: WooCommerce Matomo Analytics plugin.
- Fix: Eshock deactivated the plugin.
- No immediate need to re-enable it; impact on WooCommerce analytics to be assessed later if needed.
✅ /services Page Tile Display — RESOLVED
The /services page is now correctly rendering service tiles. The Bookly booking flow (mock pages only, not yet published) routes to /appointments.
Action Items
| Owner | Action | Due |
|---|---|---|
| Kimberly | Research Bookly docs — confirm viability of $0 service + card-capture workflow; assess whether to replace Bookly | This weekend (before Tuesday call) |
| Kimberly | Review Loom walkthrough and Miro board from Melissa | This weekend |
| Melissa | Audit all Zapier accounts — confirm no active integrations remain from Chris's work | ASAP |
| Roxana | Forward original Square support email (from Lisa's inbox) detailing the ~12 affected products | ASAP |
Context & Notes
- The next team call is Tuesday.
- Melissa noted in passing that the Bookly–Square integration via Zapier is not unprecedented — other implementations exist — which makes the current difficulty more frustrating.
- Kimberly flagged that this investigation is not a quick documentation scan; she expects it to require a significant block of focused work.
- Chris Ostergaard has transitioned away from Asymmetric. The Zapier accounts he managed may not have been fully cleaned up on departure.
Related
- [1]
- [2]