1) Overview
Use WeSupply’s shipping settings to require a signature on FedEx shipments (e.g., Indirect, Direct, or Adult signature). This applies to labels you generate in WeSupply—commonly for exchanges/replacements and returns-to-customer shipments—so carriers enforce a handoff at delivery.
2) Before You Begin
- You have Admin access to WeSupply.
- Your FedEx account is connected (directly or via a provider like EasyPost).
- You know which signature level you need (Indirect, Direct, or Adult).
- You understand any extra carrier fees and compliance rules for Adult Signature.
3) Step-by-Step Instructions
Step 1 — Navigate to Carriers
- Go to Settings → Carriers → Return Carriers.
Step 2 — Select Carriers
- Look for FedEx on your carriers, and set it as your default carrier.
Step 3 — Toggle on Delivery Confirmation
- Scroll down to the Delivery Confirmation section and turn the toggle to on.
- Save your changes.
4) Best Practices
- Set expectations: mention “Signature required” in customer emails/SMS.
- Mind delivery attempts: signature services may affect the number of attempts and pickup alternatives.
5) Troubleshooting / FAQ
The Signature option isn’t visible.
- Confirm Carrier = FedEx in the logic; some services or carriers don’t support signature.
- Verify your integration (FedEx or EasyPost→FedEx) is Active and the chosen Service supports signature.
Label was created but courier didn’t require a signature.
- Re-check the logic and regenerate the label ensuring the Signature Required level is saved.
- Confirm the service used supports the selected signature type for the destination.
Adult Signature failed at delivery.
- The recipient must meet the legal age for the destination and present valid ID. Provide guidance in your shipping confirmation.
6) Summary
In Return/Exchange shipping settings, choose FedEx and a Service, then set Signature Required (Indirect, Direct, or Adult) and Save. Generate a test label to confirm the requirement is applied. Communicate expectations to customers and use rules to balance security vs. cost.
Comments
0 comments
Article is closed for comments.