Redesigning a WooCommerce account area becomes much more complex when different customer programs need different content, approvals, saved data, and ERP-driven account information. In one project, Freshy was asked to modernize a logged-in experience that had grown around a mix of WooCommerce, Gravity Forms, TI WooCommerce Wishlist, Advanced Custom Fields, custom theme templates, and user metadata.
The work began as a smaller account cleanup but expanded after technical review uncovered broken saved-address output, outdated wishlist functionality, and a representative-assignment workflow that no longer matched the current registration behavior. The revised plan added four customer programs, Gravity Forms Pending Activations, program-specific benefits and service content, and a future Syteline integration for Studio tier and year-to-date spend data.
As of the latest documented update, Phase 1 was actively being built on staging and the ERP integration requirements were still being coordinated with the client’s IT team. No production launch had yet been documented.
Issue background
The original request focused on improving the logged-in WooCommerce experience for retail and trade users.
The account area included several custom features:
- A “My Folders” section powered by TI WooCommerce Wishlist.
- Role-specific account content.
- Saved shipping-address functionality.
- A “My Showroom” area tied to an assigned representative.
- Separate retail and trade registration flows built with Gravity Forms and the Gravity Forms User Registration Add-On.
- Custom WooCommerce account templates in the active theme.
The initial goals were to repair the broken folder experience, clarify how account data was stored, improve the account heading for different user types, and document how representative assignment worked.
A later requirements update expanded the project significantly. Instead of only two account types, the site needed four program experiences:
- Summit Retail.
- Studio.
- Studio International.
- Captains.
The client also wanted Studio users to eventually see ERP-driven data such as trade tier and year-to-date spend inside the WordPress account area.
Diagnosis
The first technical problem was the broken “My Folders” page.
The page used the shortcode:
[ti_wishlists_manage_lists]
but the site was running the free version of TI Wishlist. The custom theme and existing workflow expected premium multi-folder functionality that the installed package did not provide.
Freshy confirmed that installing TI WooCommerce Wishlist Premium restored the missing shortcode and the underlying folder-management capability. The existing wishlist templates already matched the Premium version, so they did not need a full rewrite.
Further review uncovered two additional issues that were not obvious in the initial scope.
The saved-address template was outdated. The theme’s Address Book template had been built around an older version of the plugin while the site was running a newer release. The extra-address data still existed, but the account page no longer displayed it correctly.
The representative-assignment workflow was broken. The existing logic attempted to assign a representative before Gravity Forms had saved the user’s country. The UK mapping also omitted the GB country code, and a later Gravity Forms change meant the representative picker no longer aligned reliably with the intended country rules.
As the requirements evolved, the client decided to simplify both of those areas rather than preserve the older architecture:
- The account would show one main address instead of rebuilding the multiple-address interface.
- The old “My Showroom” and Customer Support cards would be replaced with one service card driven by country.
- Folder estimate requests would route to regional service addresses rather than an assigned representative.
The project also needed a safer trade-application model. The client wanted applicants to be unable to log in until approved. Freshy confirmed that Gravity Forms Pending Activations could support this without a custom approval engine.
Resolution steps
The documented implementation plan and active staging work included:
- Use TI WooCommerce Wishlist Premium for folders. The Premium plugin was installed and the missing folder-management shortcode became available.
- Validate folders across all four account programs. The final implementation needed to verify existing folders and folder-management behavior for Summit Retail, Studio, Studio International, and Captains users.
- Create the new WordPress roles. Three new roles were required so the account experience could distinguish the four programs.
- Replace hard-coded Trade role checks. The site contained multiple places where custom code checked specifically for the old Trade role by name. Those checks needed to be updated for the new program model.
- Make account headings role-aware. The WooCommerce My Account heading would change based on the user’s assigned program.
- Simplify address handling. The revised plan moved to one primary address per user in the main account-information area. Existing extra addresses could remain stored without being displayed.
- Replace the Shipping card with My Benefits. Each program would receive its own benefits content.
- Create program-specific Full Benefits pages. The client later clarified that Studio, Studio International, and Captains each needed a distinct full-benefits page instead of a single shared page.
- Replace My Showroom and Customer Support with one Service card. The service contact would vary by country, using a US contact block for US users and an international contact block for everyone else.
- Route folder estimate requests by region. US accounts would send requests to the US service address; non-US accounts would use the international service address.
- Use Gravity Forms Pending Activations for trade applicants. Applicants would not receive usable accounts until staff approved them.
- Assign the final program after approval. Approved applicants could then be placed into Studio, Studio International, or Captains.
- Update export logic for the new roles. Existing trade-user export functionality needed to recognize the replacement program roles.
The ERP portion was designed as a separate but related workstream.
The client’s IT team identified Syteline as the primary source for Studio tier and year-to-date spend data. The planned integration used a Syteline customer number as the account-matching key.
The current integration design called for:
- A Syteline customer-number field stored in WordPress.
- Manual entry of tier, YTD spend, and rush-fee information so the account experience could launch even if automation was not ready.
- A small read-only endpoint that the client’s IT team could use to retrieve customer numbers associated with website accounts.
- A secure endpoint to receive once-daily tier and YTD updates.
- Power Automate as the initial delivery mechanism.
- A static-IP server as a fallback if firewall rules blocked Power Automate.
The integration also had to account for one important data-model change: one Syteline customer number could be associated with multiple website users, and the customer-number field could also be blank.
Freshy therefore planned the update logic so that when ERP data arrived for a customer number, every Studio contact connected to that same customer number could receive the same tier and YTD values.
The client’s IT team proposed a payload structure similar to:
{
"customers": [
{
"ERPID": "C012345",
"YtdAmount": 123456.78,
"TradeTier": 2
},
{
"ERPID": "C055555",
"YtdAmount": 8900.00,
"TradeTier": 1
}
]
}
Freshy confirmed that this structure could be supported, but endpoint details still needed to be finalized before the client’s IT team could begin sending sample data.
Final outcome
The source history does not yet document a finished production launch.
As of November 12, Phase 1 was actively being built on staging and remained on track for the November 16 target. The revised benefits-page requirement had been accepted without changing that target.
The Syteline integration was still being coordinated with the client’s IT team. Freshy had confirmed the expected customer-number matching model and payload approach, but the endpoint details and test payload had not yet been completed in the source task.
The verified progress at that point included:
- TI WooCommerce Wishlist Premium installed and the missing folder shortcode restored.
- The final four-program account model defined.
- Gravity Forms Pending Activations selected for the approval workflow.
- The old representative-based service model replaced in the implementation plan with regional service routing.
- The Syteline customer-number model refined to allow shared IDs across multiple website users.
- The once-daily ERP update payload format reviewed and accepted conceptually.
The broader lesson is that a WooCommerce account redesign should begin with a real audit of the existing account architecture. Legacy shortcodes, custom theme templates, old role names, user metadata, Gravity Forms feeds, and third-party plugins can all encode assumptions that are easy to miss during a visual redesign.
ERP integration adds another layer: the safest account-matching key is not always an email address, especially when one business account can have multiple contacts. A stable external customer ID, carefully mapped in WordPress and tested against shared-account scenarios, is usually a stronger foundation.
If your WooCommerce account area needs role-based program content, approval workflows, or ERP-driven customer data, contact Freshy. Our WordPress team can audit the existing account architecture, repair broken integrations, and design the data flow before production changes are made.