Skip to content
This repository has been archived by the owner on Feb 24, 2022. It is now read-only.

WIP As USPS system that has recovered from an outage, I am able to receive batches of orders from TTS. #44

Open
porta-antiporta opened this issue Jan 10, 2022 · 5 comments
Labels

Comments

@porta-antiporta
Copy link
Collaborator

No description provided.

@porta-antiporta porta-antiporta changed the title As USPS system that has recovered from an outage, I am able to receive batches of orders from TTS. WIP As USPS system that has recovered from an outage, I am able to receive batches of orders from TTS. Jan 10, 2022
@hartsick
Copy link
Contributor

Blocked on requirements from USPS

@porta-antiporta
Copy link
Collaborator Author

porta-antiporta commented Jan 14, 2022

Notes on call from USPS:
2 options

  • web service API

    • API were running, may not be available
  • format a file to drop into fulfillment thing

    • fixed width field formatted file
    • 25 attributes
    • 1 line per order
    • 100K orders/file

2 data transfer services

  • SFTP exchange (encryption is used)?

@porta-antiporta
Copy link
Collaborator Author

@porta-antiporta
Copy link
Collaborator Author

porta-antiporta commented Jan 14, 2022

⚠️ first name 25 char
⚠️ last name 25 char
❗ email is limted to 50 char

My gut is we don't limit name on our application, but accept that it gets truncated by USPS. This shouldn't impact deliverability. Address, given we are standardizing to USPS, should be OK.
It's email that if it gets truncated, user wouldn't receive status updates.

@hartsick
Copy link
Contributor

Adding here that we will likely need to do some character replacement to allow conversion from UTF-8 -> ASCII. Here's Ryan's POC: "Ryán".encode("ASCII", fallback: ->(orig) { 'a' })

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants