When creating an order, I lose my progress when I login

If you’re losing your progress when you login while creating an order, it may be because you have an old file saved in your browser’s cache. You can fix this by clearing the cache in your browser. If you’re not sure how to do this, just follow the steps below for the browser you’re using:

Chrome

  1. Click the icon with the 3 dots in the top right corner of your browser
  2. Go to “More tools” then “Clear browsing data”
  3. On the popup that appears, you’ll want to set the time range to when the issue first appeared, you can select “All time” to be sure
  4. Make sure you have “Cached images and files” ticked. You don’t need the other options ticked
  5. Click “Clear data”
  6. Now retry sending your parcel and this issue should be fixed

Safari (Mobile)

  1. Go to “Settings” and then “Safari”
  2. Tap “Clear History and Website Data”
  3. Now retry sending your parcel and this issue should be fixed

Safari (Desktop)

  1. Click on the “Safari” drop-down menu
  2. Select “Preferences”
  3. Click the “Advanced” tab, then tick the “Show Develop menu in menu bar” option and close the Preferences menu
  4. Select the “Develop” drop-down menu and click “Empty Cache”
  5. Now retry sending your parcel and this issue should be fixed

Edge

  1. Click the icon with the 3 dots in the top right corner of your browser
  2. Go to “Settings”
  3. Click on “Privacy, search, and services” in the left-hand panel
  4. Scroll down to “Clear browsing data” and select “Choose what to clear”
  5. Click the slider next to “Cached images and files”
  6. Close and reopen your browser and this issue should have been fixed

Firefox

  1. Click the menu icon at the top right of the browser
  2. Select “Settings”
  3. Click “Privacy & Security” in the left-hand panel
  4. Under “Cookies and Site Data”, select “Clear Data…”
  5. Make sure “Cached Web Content” is ticked (“Cookies and Site Data” doesn’t need to be ticked) and click the “Clear” button
  6. Retry sending your parcel and this issue should have been fixed
Was the information helpful?