Doudlah Farms — Seller Central Access & Email Management
Overview
During the October 2025 marketing call, two distinct Seller Central access problems were identified and partially resolved for Doudlah Farms. The first — Lucy's employee permissions — was fixed live on the call. The second — the primary account's non-existent email address — remains open pending Amazon Seller Support intervention.
Related client: [1]
Problem 1: Lucy's Employee Access
Background
Lucy had been invited to Seller Central as an employee user but was unable to access the account under her own credentials. She had been logging in using Mark's credentials as a workaround, which created confusion and a lack of individual accountability.
Root Cause
A UI bug in Seller Central's user permissions flow: checking the top-level "Grant University" checkbox did not automatically select all sub-permissions beneath it. Lucy's account existed in the system but had effectively no permissions granted.
Resolution (Completed on Call)
- Lucy logged in using Mark's credentials and navigated to Settings → User Permissions.
- The team located Lucy's account (which had appeared in the system after re-accepting the invitation and selecting the correct marketplace region — US).
- Rather than relying on the top-level checkbox, the Admin box for each individual permission section was manually checked.
- Changes were saved. Lucy then logged out and back in under her own credentials and confirmed full access.
Status: Resolved.
Problem 2: Primary Account Email — Non-Existent Address
Background
The primary Seller Central account is registered to mark@doudlahfarms.com. This email address does not exist — the domain email was discontinued at some point and never updated in Amazon's system. Gilbert confirmed this by attempting to send a message to the address, which bounced.
Risk
Amazon sends critical communications (policy alerts, account health warnings, verification requests) to the primary account email. If these messages bounce undetected, Doudlah Farms could miss time-sensitive compliance actions and risk account suspension.
Attempted Fix & Blocker
During the call, Lucy attempted to update the primary email to mark.r.doudlah@gmail.com via Settings → Account Info → Login Settings → Change Email. Amazon rejected the change with the error:
"The new address provided is already taken."
Cause: mark.r.doudlah@gmail.com is already associated with Mark's personal Amazon shopping account. Amazon does not allow the same email to be used across a consumer account and a Seller Central account simultaneously.
Options Discussed
| Option | Notes |
|---|---|
Change primary email to mark.r.doudlah@gmail.com |
Blocked — already tied to personal account |
| Delete/merge personal Amazon account first | Mark indicated he doesn't care about the personal account; feasibility TBD |
Restore mark@doudlahfarms.com via GoDaddy |
Possible but requires paying to reactivate the domain email |
Use lucy@doudlahfarms.com as primary |
Discussed but not pursued — would mismatch account holder name |
Next Step
Gilbert is responsible for contacting Amazon Seller Support to determine the correct path forward — likely either merging/removing the personal account or finding an alternative resolution that allows mark.r.doudlah@gmail.com to be used for Seller Central.
Status: Open — assigned to Gilbert.
Action Items
- [x] Fix Lucy's employee permissions in Seller Central (completed on call, 2025-10-24)
- [ ] Contact Amazon Seller Support to resolve primary account email conflict — change from
mark@doudlahfarms.comtomark.r.doudlah@gmail.com; advise on personal account conflict (@Gilbert)
Key Contacts
| Name | Role | |
|---|---|---|
| Lucy Doudlah | Operations / day-to-day Seller Central user | lucy@doudlahfarms.com |
| Mark Doudlah | Account owner (primary credential holder) | mark.r.doudlah@gmail.com |
| Gilbert Barrongo | Asymmetric — Amazon account manager | gilbert.barrongo@asymmetric.pro |
Related Notes
- [2]
- [3]