Amazon SP-API Developer Registration — 2026-04-05

Overview

Working session between Mark Hope (Asymmetric Applications Group) and Sherry Lucy Doudlah to register Mark as an Amazon SP-API developer on the Doudlah Farms Seller Central account. Registration was submitted successfully after resolving two form validation errors. A critical account owner email issue was identified but not fully resolved during the session.

Attendees: Mark Hope (mark.hope@asymmetric.pro), Sherry Lucy Doudlah

Key Decisions

• Registered Mark Hope under Asymmetric Applications Group as a Private Solution Provider — not a public app developer.
• The "Restricted" data role was deselected to avoid triggering an Open Banking registration requirement that does not apply to this engagement.
• Confirmation emails are expected at mark.hope@asymmetric.pro (the primary contact on file), not the defunct mark@doodlafarms.com owner address.

Registration Details

Navigation path used:
Seller Central → Hamburger menu → Apps & Services → Develop Apps → Build Applications that Use SP-API → Apply → Setup Solution Provider Account Profile

Form Errors Encountered & Resolved

Error 1 — "Restricted" Role Selected

• Problem: A role marked "Restricted" (related to direct-to-consumer shipping / PII) was selected. Amazon requires a separate Open Banking registration for any restricted role.
• Resolution: Deselected the restricted role entirely.

Error 2 — Open Banking Identifier Field Left Blank

• Problem: Even after deselecting the restricted role, the Open Banking Identifier field remained required by the form.
• Resolution: Entered N/A in the field to satisfy the validation requirement.

After both fixes, the registration submitted successfully.

Critical Issue: Defunct Account Owner Email

The Seller Central account owner is listed as Mark R. Doudla with email mark@doodlafarms.com. This email address was discontinued long ago and is no longer accessible.

Consequences:
- Password resets for the owner account cannot be completed.
- During this session, a new password was set and used successfully by Mark Hope, but Sherry was unable to log in with the same credentials — login failed with "incorrect password."
- The owner account represents a single point of failure for any actions requiring owner-level access.

Attempted fix: A temporary password was created during the session. Mark Hope was able to authenticate with it, but Sherry could not replicate the login. Root cause unclear — possibly a session/cache issue or account state problem.

Action Items

• [ ] Mark Hope — Monitor mark.hope@asymmetric.pro for SP-API developer registration confirmation email. Check Seller Central case log (~Feb 13) for registration status.
• [ ] Sherry Lucy Doudlah — Attempt to update the account owner email (mark@doodlafarms.com) to a functional address via Account Info in Seller Central.
• [ ] Sherry Lucy Doudlah — If self-service email update fails, open an Amazon Seller Central support case to remove the defunct owner email and replace it with an active address.
• [ ] Both — Revisit the developer portal in a few days to confirm registration status.

Relevant Transcript Excerpts

Mark Hope [~08:38]: "It's Mark at DoodlaFarms.com. Do you have a way to get to that email?"
Sherry Lucy Doudlah: "No. Because we discontinued that email a long time ago."

Mark Hope [~48:14]: "Hopefully not, because it'll be in this case log. We come back in a day or so and check it... it says primary email is my email, so hopefully it'll come to me."

Sherry Lucy Doudlah [~48:28]: "We need to take Mark at DulaFarms.com out. There is no email."
Mark Hope: "I think we're going to have to create a case."

Related

• ^[1]
• ^[2]