Know what the Contact Shipper and Send Shipment buttons do, why public visitors are redirected, and which client profile or contract condition controls the next screen.
Who can do this
- Anyone can inspect the calls to action.
- A signed-in Client with a completed profile is required to create a conversation or contract request.
Before you start
- Review the shipper profile and decide whether the next need is a question, a contract request, or work under an existing active contract.
- Use or create a Client account, not a Shipper account, for buying fulfillment services.
Steps
- Choose Contact Shipper when you need to clarify services, pricing drivers, facility constraints, schedule, returns, or fit before signing.
- Choose Send Shipment when you are ready to review and request the relationship. The label does not mean a shipment is immediately created when no active contract exists.
- If signed out, either action routes to Login. Sign in with the intended Client account, then return to the same shipper profile from search/history.
- If Profile Completion Required appears, choose Complete Profile and save the required client business, address, typical-case/volume, categories, and warehouse requirements.
- After profile completion, Contact Shipper creates or reuses a conversation and opens Client > Messages with the shipper selected.
- After profile completion, Send Shipment checks for an existing contract. Without one it opens the agreement; with an active existing contract it shows Create Shipment and opens shipment creation for that shipper.
- After sending a contract request, follow its state in Client > Contracts instead of repeatedly returning to the public button.
Fields and decisions
- Contact is for questions and creates a message record. It does not request a contract or reserve warehouse space.
- Send Shipment is context-sensitive: agreement first for a new relationship; shipment creation for an existing contract.
- Profile completion gives the shipper useful operating context and is required before communication/relationship actions.
- Sign-in redirects do not automatically preserve every unsaved public page state; remember the shipper name or reopen it from search.
- A Client role buys fulfillment. A Shipper role provides fulfillment and cannot use the client action path as if it were a merchant.
- A pending contract is not equivalent to an active contract even if the profile still shows calls to action.
Finished when
- A question opens the intended conversation, or a relationship request appears in Contracts, or an existing active relationship opens Create Shipment.
- No duplicate conversation/contract was created to work around navigation.
What this changes
- Contact Shipper can create a conversation and notify the shipper according to notification preferences.
- Signing the agreement creates a contract request. Create Shipment begins an operational draft only under the existing relationship path.
Common problems
You return from Login but are not on the same profile.
Run the location search again or use browser history, then reopen the remembered shipper.
Profile completion keeps appearing.
Open Client Profile and confirm required business/address/fulfillment sections saved successfully; then refresh the shipper profile.
Contact creates no visible conversation.
Open Client > Messages and check for the shipper before retrying. Repeated clicks can target the same conversation.
Send Shipment opens an agreement instead of shipment creation.
There is no recognized active contract with this shipper. Review Client > Contracts and follow the request/approval path.
Safety checks
- Do not put payment credentials, API secrets, identity documents, or passwords in a shipper message.
- Do not bypass the contract/official shipment workflow by sending inventory based on public contact details.
- Contact support when the correct Client account and completed profile loop between Login/Profile, a conversation cannot be opened after one creation attempt, or an active contract is not recognized by Create Shipment. Include shipper and account email, not passwords.
Owner: Fulfield Product Support | Content version: 2026.09.01.1 | Last verified: 2026-09-01