Contact person: FastAPI Shipping Label Queue Integration

Phone:Show

Email:Show

Location: Lorain, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"This project centers on extending an existing FastAPI back-end so it can pre-generate shipping labels, place them in a queue, and push them into the [login to view URL] platform that runs our fulfilment workflow.

Core flow
• A request comes in through FastAPI.
• The service immediately generates a PNG label (no other formats needed) and stores it in a queue for downstream processing.
• Once queued, the label data is sent to [login to view URL] so our team can bulk-print everything from within that system.

Key points to keep in mind
• Labels must be produced in batches large enough for smooth bulk printing.
• Queuing should be resilient—Redis, RabbitMQ, or a similar broker is fine as long as retries and failure handling are covered.
• The codebase must remain idiomatic FastAPI (Pydantic models, dependency injection, async awareness).
• [login to view URL]’s API is the sole integration target; no FedEx, UPS, or DHL endpoints are necessary.
• Output files are PNG only, delivered via an S3 bucket or another pluggable store that [login to view URL] can pull from.

Deliverables
1. FastAPI endpoints (generate label, fetch status).
2. Queue worker script with clear run instructions.
3. [login to view URL] integration module (auth, label push).
4. README covering environment variables, setup, and a sample bulk-print run.

Acceptance criteria
• Generating 100+ labels in one call completes without timeout and every label reaches Fulfil.io.
• Failed pushes automatically retry up to three times and surface clear logs.
• A simple pytest suite confirms the above behavior." (client-provided description)