Your Amazon FBA ship-from address identifies the shipment’s source, not the Amazon warehouse receiving it. Amazon’s Fulfillment Inbound API requires a source address when creating an inbound plan; its shipment-address update operation allows changes only before carrier confirmation and invalidates existing transportation options when the source changes.

Those rules come from Amazon’s official SP-API model, checked November 20, 2026. This guide separates documented API requirements from Seller Central screens that have not been tested here. Use it to prepare a warehouse handoff, diagnose address mismatches, and avoid treating an old transportation quote as current after a move.

What your Amazon FBA ship-from address identifies

Amazon’s official ShipmentSource definition describes the shipment’s ship-from address. Separately, CreateInboundPlanRequest requires sourceAddress, using the AddressInput structure. These names matter when your shipping software asks for details that differ from the labels in your account.

Keep these address roles separate:

Address or identifierWhat it representsWhat to check
Shipment source addressWhere the inbound shipment originatesMatch the facility handling that shipment’s dispatch
Amazon ship-to addressThe shipment’s receiving locationUse the destination associated with the shipment, not the source record
Registered business addressYour business identity recordDo not copy it automatically when inventory leaves another facility
destinationMarketplacesThe marketplace selection in the inbound-plan requestIt is not a street address or a substitute for a shipment destination

For example, suppose your company receives mail at an office while a prep center dispatches the cartons. Prepare the address handoff around the prep center’s dispatch location rather than copying the office address by habit. Ask the facility which street entrance and unit identify the shipping operation.

If you need the full shipment-creation sequence, start with how to ship to Amazon FBA. This guide focuses on source-address data and address changes, not packing, placement selection, or the complete Send to Amazon workflow.

Required API fields: what Amazon’s schema actually says

As checked November 20, 2026, Amazon’s AddressInput schema lists the following required properties. These are API-schema requirements, not a claim that every Seller Central form has identical required fields. Country-specific validation and your shipping software’s checks can require additional information.

Required propertyMeaning in the modelPreparation check
addressLine1Street address informationConfirm the dispatch facility’s street address
cityCityMatch the facility’s address record
countryCodeTwo-character ISO 3166-1 alpha-2 country codeUse an uppercase country code, such as US or CA
nameIndividual who is the primary contactObtain a contact for the source facility
phoneNumberPhone numberConfirm that it reaches the appropriate shipping contact
postalCodePostal codeCheck it against the street address, not just the city

The same schema contains these properties without listing them as required:

Property not in the required listMeaningPractical use
addressLine2Additional street address informationInclude the suite, unit, or other relevant location detail
companyNameBusiness nameIdentify the company operating at the source
districtOrCountyDistrict or countySupply when relevant to the facility’s address
emailEmail addressProvide an appropriate contact if requested by the workflow
stateOrProvinceCodeState or province codeCollect it where relevant; omission from this list is not permission to omit it from every shipping form

Required status is only one part of validation. The model also defines field lengths and a country-code pattern. For instance, countryCode uses ^[A-Z]{2}$: a spelled-out country name is not the value that property expects. A structurally acceptable code also needs to identify the correct country.

For an integration, distinguish an omitted optional property from an empty string. Several optional properties, including addressLine2 and companyName, have a minimum length of one when supplied. A blank value is therefore not interchangeable with leaving the property out of the request.

The contact fields deserve a separate check. The model describes name as an individual, while companyName identifies the business. Putting a warehouse company name into every contact field loses that distinction. Keep both values in your handoff even if your current form combines them differently.

Collect a warehouse-ready address handoff

Ask the party preparing the shipment to verify one address record before anyone confirms transportation. A supplier, prep center, and freight forwarder may each have an address associated with the inventory; the useful record is the one that describes the source for the shipment you are actually arranging.

Use this copyable request:

Please confirm the dispatch facility’s street address, additional unit or suite details, city, state or province where applicable, postal code, and uppercase country code. Include the operating company, primary contact’s name, and phone number. Please distinguish this location from your billing office and identify any separate pickup instructions.

Keep the reply with the shipment’s working records. Record the inbound plan and shipment identifiers alongside it so that a correct address is not accidentally applied to the wrong shipment. For software-managed shipments, ask the integration operator to compare the submitted source data with this facility-confirmed record.

Check the handoff in three passes

Location: Compare the street, city, postal code, and country together. A familiar city name can hide a wrong postal code or an old branch address. If cartons move from one facility to another before dispatch, revisit which location the shipment record describes.

Contact: Verify the contact’s role and phone number with the dispatch facility. A supplier’s sales representative may not handle carrier queries. Keep operational contacts separate from the seller account’s owner details unless they are genuinely the same person.

Instructions: Keep address data distinct from pickup arrangements. A unit number belongs in the location details; a loading-window instruction is not a replacement for a street address. Ask the carrier or shipping provider where to record access and appointment information in its workflow.

This handoff also helps when two people work on the same shipment. Assign one person to approve the source record and another, if needed, to arrange transportation. Before booking, have the transportation operator check the approved record rather than retyping it from a message thread.

Change the address before carrier confirmation—not merely before dispatch

Amazon’s updateShipmentSourceAddress operation provides the central timing rule. Its official description, checked November 20, 2026, says:

The shipment source address can only be updated prior to the confirmation of the shipment carriers.

The same description states that updating the source invalidates existing transportation options, which must be regenerated to reflect potential differences in options and quotes. An address edit is not just a cosmetic correction to an otherwise unchanged booking.

Read the boundary this way:

Create inbound plan with a source address
                  |
       Check shipment source details
                  |
If changing the source before carrier confirmation:
Update source -> existing transportation options invalidated
              -> regenerate options -> review current quote
                  |
          Confirm shipment carrier
                  |
The documented source-update window has closed

This is a decision map based on the API description, not a screenshot or a reproduction of Seller Central’s screen order.

For software-managed shipments, use the following sequence:

  1. Identify the affected inbound plan and shipment, and establish whether the shipment carrier has already been confirmed.
  2. If still within the documented update window, submit the corrected source through the supported integration workflow.
  3. Check the address-update operation’s outcome. The API documents a 202 response with an operationId; receipt of that response alone is not proof that replacement transportation options exist.
  4. Regenerate transportation options after the source update succeeds. Reopen the selection using the newly generated options rather than reusing a saved choice from the old address.
  5. Review the current service and quote before carrier confirmation. Update the warehouse handoff so the physical dispatch location agrees with the corrected record.

Amazon’s description says the new address can produce different options and quotes. It does not say that every address correction increases the price, or that a nearby move leaves the price unchanged. Review the actual replacement options instead of applying either assumption.

A truck not having arrived is not the deciding condition in this API rule. Carrier confirmation can precede physical dispatch; check the confirmation state rather than relying on a warehouse message saying the cartons are still there.

Troubleshoot mismatches without guessing Seller Central rules

Start with the symptom and separate missing data from a closed update window. The following checks do not depend on a particular Seller Central button label.

SituationFirst checkNext action
Address rejected during plan creationRequired properties, country-code format, and supplied field valuesCorrect the record; inspect the returned error rather than adding random abbreviations
State or province requested despite being outside the schema’s required listThe current form or integration’s validation messageSupply the applicable location data; the model’s required list does not override the form
Corrected address but an old quote remains in a spreadsheetWhether transportation options were regenerated after the changeCompare against newly generated options, not the historical quote
Shipment now leaves a different prep centerShipment source and carrier-confirmation stateResolve the address before confirming transportation where the documented operation permits
Carrier already confirmedThe exact shipment and booking stateUse the workflow’s supported resolution path; do not assume the source-update operation remains available

If you work only in Seller Central

Use the field checklist to collect accurate information and check the controls available for the shipment’s current state. This article does not establish a universal click path, an Edit button name, or identical country-specific form behavior. The public API operation documents what an integration can request; it does not prove that Seller Central exposes the same action at the same place.

If the current workflow does not offer a source change, gather the shipment ID, current source, intended source, and carrier-confirmation details before asking Seller Support or your shipping provider for the applicable resolution. That gives them a concrete mismatch to investigate rather than an open-ended address question.

For a confirmed shipment that may need cancellation or replacement, see canceling an Amazon FBA shipment. Treat cancellation, transportation-charge handling, and source-address editing as separate questions. This API description does not establish a fee-free cancellation window or promise that changing an address reverses a charge.

Final handoff checklist

Before confirming transportation, check the record that the booking will actually use:

  • Source: The dispatch location is not confused with the Amazon receiving address or your billing office.
  • Identity: The inbound plan and shipment identifiers match the shipment being arranged.
  • Fields: The source contains the required API properties where applicable, plus the location details requested by your workflow.
  • Contact: The contact name and phone number belong with the source facility’s shipping operation.
  • Change state: Any source correction has been completed before the documented carrier-confirmation boundary.
  • Transportation: Options have been regenerated following a source update, and the selected quote comes from that refreshed set.
  • Warehouse copy: The dispatch facility and transportation operator are working from the same approved address.

Save the approved source record with the current transportation selection. If someone later asks why a quote changed, that record makes it possible to distinguish an address change from a service-selection change without reconstructing the booking from memory.

Frequently Asked Questions

Does changing my business address automatically change an FBA shipment’s source?

The cited inbound API model does not document such an automatic link. It defines source-address data for inbound plans and shipments. Check the affected shipment’s source separately rather than assuming an account-profile edit updates an existing shipment.

Can I put a prep center’s company name in the contact-name field?

Amazon’s AddressInput model distinguishes companyName, the business name, from name, the individual who is the primary contact. Collect both from the prep center and map them to the fields your workflow requests. Do not assume they are interchangeable just because both refer to the same facility.


Sources

  • Amazon’s official Fulfillment Inbound API v2024-03-20 model, checked November 20, 2026. Relevant definitions: CreateInboundPlanRequest, AddressInput, and ShipmentSource; relevant operation: updateShipmentSourceAddress. This is the published API contract, not evidence of an authenticated Seller Central UI test.