Getting Started on Modern Dropship
Chat
Passwordless Sign-in
Step by Step for Buyer Onboarding
Step by Step for Seller Onboarding
Successful Support Interactions
System Status
Integrations
Shopify
WooCommerce
Adding Barcode Values in WooCommerce
Connecting WooCommerce
How can I confirm that Modern Dropship can pull my Products from my WooCommerce Store?
Updating your WooCommerce URL
Magento 2
BigCommerce
CSV managed account
Connecting through SFTP
Downloadable Image Links
Fixing SKUs in Scientific Notation
How to Resolve " Your SFTP user requires delete permission on your SFTP server."
How to Resolve "Unable to access your SFTP server"
How to Resolve "Your SFTP user requires read permission on your SFTP server"
How to Resolve "Your SFTP user requires write permission on your SFTP server."
Importing Products using a CSV file in the Modern Dropship web app
Manual Fulfillment
API
Building API Integrations
Getting Started with Webhooks
Getting Started with the Buyer API
How to Create an Order for the Buyer API
Webhook FAQ
EDI
Connecting through Seller EDI - Invoice (810) Specification
Connecting through Seller EDI for Dropship
Connecting through Seller EDI for Dropship - Advance Ship Notice (856) Specification
Connecting through Seller EDI for Dropship - Inventory Update (846) Specification
Connecting through Seller EDI for Dropship - Purchase Order (850) Specification
Connecting through Seller EDI for Dropship - Purchase Order Acknowledgements (855) Specification
Downloading EDI Files
How to Create a Test Order as an EDI Seller
How to Resend an Advance Ship Notice
How to Resolve "Already Processed Files"
Seller EDI Quick Reference
EDI - Fall 2024 and later
Advance Ship Notice (856) Specification
Connecting through Seller EDI
Inventory Update (846) Specification
Invoice (810) Specification
Purchase Order (850) Specification
Purchase Order Acknowledgements (855) Specification
Seller EDI Quick Reference: Fall 2024 and later
Migrating Ecommerce Platforms
Supported Connection Methods
Account Management
Connecting Easypost
How to Change Your Commerce Type
Integrating your CRM
Inviting Team Members
Managing Issues
Managing Multiple Accounts
Managing Notifications
Reporting
Setting Billing Address
Viewing Subscription Info
Partners
Actions & Action Templates
Adding Partners
How to Determine the Remaining onboarding steps for a Partner
Seller SLAs
Products
Autonomous Merchandising
Buyer Product Validation Guide
Exclusive Collaborations - Syncing Unpublished Products
How Inventory Sync Works
How to Solve Shopify "Item Not Recognized" Error
Marking Products as Active or Inactive
Selecting Products
Pricing
Create a Price List For a Smaller Catalog
Editing Price Lists
How to Set Up Pricing
Price List FAQs
Promotional Price Lists and Discounts
Orders
Cancelling Orders
Check Order Status
Fixing an Order Sync Timeout Error
Fulfilling orders from your ecommerce platform
Handling Returns
Packing Slips - Buyers
Packing Slips - Sellers
Sending Test Orders
Invoicing
Configuring Per-Order Fees
How Invoicing Works
How to Delay an Invoice
Partnership Billing Settings
Understanding Per-Order Fees
Platform
General Dropship Information
- All Categories
- Orders
- Fixing an Order Sync Timeout Error
Fixing an Order Sync Timeout Error
Fixing an Order Sync Timeout Error
A timeout error occurs when Modern Dropship posts an order to your platform but doesn't get a reply back. This could happen because your platform received the order but took too long during processing to reply back in time. It could also mean that your platform never received the order at all. It's important to determine which scenario happened before trying to sync the order again. Otherwise you could end up with a duplicate order in your platform.
How do I fix the error?
Step 1: Log in to your platform
You'll need to log in to the platform where Modern Dropship is syncing your orders. Often that is an ecommerce platform like Shopify, WooCommerce, or similar.
Step 2: Locate the order
Now that you're logged in to your order platform, look to see if there is an order matching the Modern Dropship order that triggered the timeout error. It's recommended to compare multiple features such as timestamp, customer name, and order items to make sure the orders are a match for each other.
Step 3: If you found the matching order...
Great! The order was posted to your platform properly. However, our system isn't aware of the matching order so we won't be able to keep the two orders in sync with each other. We call this a broken order sync.
You have two options for fixing a broken order sync:
1. Recommended. You can delete the copy of the order in your e-commerce platform (not Modern Dropship) and then resync the order from Modern Dropship again. This will fix the broken order sync by creating a fresh copy with no timeout error. To do this follow Step 4 below. If you have already started to do work on the order (or have integrations that have synced the order to another system) you may not want to use this option.
2. You can email our support team to have us fix the broken order sync without deleting the order in your platform. You will need to email support@moderndropship.com (or reply back to the timeout alert email) with the following message:
Hi, I was alerted to an order sync timeout error. The order did sync to my platform successfully and I need help to fix the syncing between the two orders. The order URL in Modern Dropship is: (fill this in). The order URL in my platform is: (fill this in). (Optionally include more information for a faster resolution time such as: a screenshot of the order in your platform).
Our support team will use this information to link the two matching orders together which will fix the broken order sync.
Step 4: If you didn't find the matching order...
This is okay. It means that the order never made it into your platform. All you need to do now is go back to the Modern Dropship order page and click the Retry button in the top-right corner to attempt creating the order again. Clicking Retry will add the order to a processing queue, so check back in the next 30 minutes to see if the sync was successful this time. If there is another error, you will also receive another alert about it.