GoatLabelsGoatLabels
For procurement and operations leads.

Shipping software RFP template and requirements checklist


Nine areas. One honest scorecard.

A shipping software RFP should cover nine areas: carriers and accounts, order intake, rate shopping, labels and printing, API, cost reporting, security, support, and pricing. GoatLabels answers it as a parcel service on USPS, UPS, FedEx, and DHL at $0 a month on Free or $40 flat on Pro. It has no SSO, no SLA, no LTL, and does not take your own carrier accounts.

Requirements you can score

Ask each vendor which carriers it quotes and on whose accounts. GoatLabels quotes USPS, UPS, FedEx, and DHL on every parcel from one account.

UPSFedExDHLUSPSall quoted
Four carriersQuoted on every parcel.
CSV or APIPlus 13 store connectors.
Parcel onlyNo LTL or freight.

Pricing you can put in the RFP

Free is $0 a month with 50 shipments. Pro is $40 a month flat with unlimited shipments. Labels are paid from a prepaid wallet with a dated ledger.

VisaMastercardAmerican ExpressApple PayGoogle PayBitcoinEthereumTether (USDT)
No contractMonth to month.
Pro $40 flatUnlimited shipments.
No SSO or SLAStated up front.
Shipping software RFP requirements, compared

What should a shipping software RFP ask every vendor?

Most shortlists mix three kinds of product: a label service like GoatLabels, a subscription shipping platform, and an enterprise multi-carrier system. They answer the same requirement in different ways, so score them on the same six areas. The last column holds the shipping software vendor questions to copy into your RFP. Verify each vendor's answer in writing.

Updated

Shipping software RFP requirements, compared, sources checked 2026-10-06
 GoatLabelsSubscription shipping platformEnterprise multi-carrier systemWhat to ask every vendor
Carriers and accountsUSPS, UPS, FedEx, and DHL plus an international network, from one GoatLabels account. Your own carrier accounts or negotiated rates cannot be added. Parcel only, no LTL.Varies by vendor and plan. Confirm whether your own carrier accounts can be connected and on which tier.Typically built around your own carrier contracts, often across many carriers and regions. Confirm the list.Which carriers and services are supported, on whose accounts, from which origin countries, and is LTL in scope?
Order intake13 store connectors, bulk CSV import of up to 500 rows per file, or the REST API. No native ERP, WMS, OMS, or EDI connectors.Usually a catalog of store and marketplace integrations. Check that yours is listed and what it syncs.Usually integrated to an ERP or WMS as an implementation project by the vendor or a partner.How do orders arrive from our systems, who builds and maintains that link, and what happens to a bad record?
Rate shopping and labelsFour carriers quoted on every parcel, one all-in number each. Multi-carton orders, PrintNode auto-print. No GS1-128 retailer compliance labels.Commonly rate shopping across connected carriers with automation rules. Ask what the quoted rate includes.Commonly rule-based carrier selection across contracted carriers, with compliance label options. Confirm scope.Is the quoted rate the amount charged, including surcharges? Which label formats and printers are supported?
API and integrationREST API with unlimited calls on every plan, live and test keys, Idempotency-Key, signed replayable webhooks, OpenAPI 3.1. No SDKs.Varies. Ask whether API access depends on the plan and whether calls are metered or capped.Varies. Ask whether integration work is done by the vendor, a partner, or your own team.Is there a public spec, a test mode, idempotent label purchase, and signed webhooks? What are the rate limits?
Security, support, and SLANo SSO, no sub-accounts, no contractual SLA, no dedicated account manager. Support is email plus an in-app assistant, with no phone line.Varies by plan. Ask which tier includes SSO, user roles, and phone or chat support.Often offered as part of a negotiated contract. Ask for the SLA and support terms in writing.Do you support SSO and role-based access? What is the uptime commitment, the remedy, and the support channel?
Pricing and contractFree $0 a month with 50 shipments, or Pro $40 a month flat with unlimited shipments. Prepaid wallet. No contract and no volume contracts.ShipStation and Shippo publish tiered plans on their pricing pages. Ask what changes between tiers.Quoted by sales. Pitney Bowes lists SendPro Enterprise pricing by request. Ask about implementation fees.What is the total yearly cost at our volume, what is the term, and what are the renewal and exit terms?

Third-party details checked on from each vendor's own pages: ShipStation pricing page (tiered plans), checked 2026-10-06; Shippo pricing page (tiered plans), checked 2026-10-06; Pitney Bowes SendPro Enterprise (pricing by request), checked 2026-10-06. Plans and features change, so confirm on the vendor's current page before you decide.

What should a shipping software RFP include?

A shipping software RFP should include nine requirement areas: carriers and accounts, order intake, rate shopping, labels and printing, API and integration, cost reporting, security and access, support and SLA, and pricing and contract. Open with a one-page profile of your operation: monthly parcel count, origin sites, typical weights, destination mix, and the systems that hold orders today.

Write each requirement as a question a vendor can answer with yes, no, or a number, and mark it as required or preferred. Vague lines such as 'robust integrations' invite marketing copy in reply. A line such as 'import 300 orders from a CSV file and report errors by row' can be tested in a trial, and it lets you compare three vendors on the same evidence. The result is a shipping software requirements checklist you can reuse for the next selection.

What carrier questions belong in a shipping software RFP?

Ask every vendor which carriers and services it supports, whose carrier accounts the labels are bought on, and which origin countries it covers. Those three answers are the core of a multi-carrier shipping software RFP: they decide whether your negotiated rates survive the move, and whether you need carrier contracts at all. Also ask whether LTL and freight are in scope, because a parcel tool may not book pallets.

GoatLabels answers as follows. It rate-shops USPS, UPS, FedEx, and DHL on every parcel from one account, with one all-in number per carrier, plus an international network, from US and Singapore origins. You cannot bring your own carrier accounts or negotiated rates, and it does not quote or book LTL. If your contract rates are a required item, score that line as not met.

How do you evaluate order intake and API requirements?

Evaluate order intake by asking each vendor to load a real sample of your orders during the parcel shipping software evaluation, not after signing. List the systems that hold orders, then ask for the exact route from each one: a named connector, a file import, or an API. Ask who builds the link, who maintains it, and what the tool does when one record has a bad address.

GoatLabels has 13 store connectors, a bulk CSV import of up to 500 rows per file that names the row and field of each error, and a REST API with unlimited calls on every plan. The API has live and test keys, Idempotency-Key support, signed replayable webhooks, and an OpenAPI 3.1 spec. It has no native ERP, WMS, OMS, or EDI connectors and no SDKs, so those routes are CSV or API work on your side.

What should the RFP ask about cost reporting and contracts?

Ask how each vendor shows what a label cost, when the charge posts, and how carrier adjustments appear later. Finance needs a cost per order or cost center without rebuilding it from carrier invoices. Then ask for the full yearly cost at your volume: subscription, per-label fees, implementation, and support tiers, plus the contract term and the renewal and exit terms.

GoatLabels charges $0 a month on Free with 50 shipments, or $40 a month flat on Pro with unlimited shipments and cheaper label rates, with no contract. Labels are paid from a prepaid wallet, and each one writes a dated ledger entry that carries your reference. Re-weigh adjustments post to the same ledger. It does not offer volume contracts, per-client balances, or automatic write-back into an ERP.

When is GoatLabels the wrong answer to a shipping software RFP?

GoatLabels is the wrong answer if your RFP marks SSO, a contractual SLA, your own carrier accounts, or LTL as required, because it offers none of them. It also has no sub-accounts, no dedicated account manager, no phone support, no retailer compliance labels such as GS1-128, and no hazmat or cold-chain services. Score those lines as not met.

It fits a narrower brief: a team that ships parcels, wants four carriers quoted without signing carrier contracts, and can bring orders in by store connector, CSV, or API. If security review requires single sign-on, or legal requires an uptime commitment with remedies, an enterprise multi-carrier system or a higher platform tier is the realistic shortlist. Use this page to rule GoatLabels in or out early.

Still defining the category? Start with B2B shipping software. Scoring API requirements? See the shipping API comparison.

Public API v1

API requirements you can test before you score.

An RFP line about integration is only as good as the test behind it. The GoatLabels REST API has unlimited calls on every plan, live and test keys, Idempotency-Key support, signed replayable webhooks, rate-limit headers, and an OpenAPI 3.1 spec, so your developer can check each line on the Free plan. There are no SDKs.

Test keys to trial the flow without buying labels
Idempotency-Key so a retry never buys twice
Signed, replayable webhooks for tracking events
OpenAPI 3.1 spec to review before you score
Read the API docs Get an API key$0 per API call
curl https://api.goatlabels.io/api/v1/shipments
POST /api/v1/shipments
Authorization: Bearer sk_live_…
Idempotency-Key: ord_8421

{
  "to": { "name": "Joyce", "city": "Berlin", "country": "DE" },
  "parcel": { "weight": 2.6, "weight_unit": "lb" },
  "service": "fedex_intl_priority"
}
Pay for labels, not a tier

Two plans. No contract.

Free is $0 a month with 50 shipments a month. Pro is $40 a month flat with unlimited shipments and cheaper label rates. Bulk CSV, 13 connectors, and the REST API come with both, and labels are paid from a prepaid wallet.

Pro

Most popular
$40/ month
Unlimited shipments on one flat plan
Cheaper label rates
Four carriers rate-shopped on every parcel
The same API and wallet as Free

Volume pricing

illustrative
less volumemore volume

pay for labels, not for seats

Free

$0 / forever

Enough to test your RFP requirements on real parcels.

50 shipments a month at $0
USPS, UPS, FedEx, and DHL rate-shopped on every parcel
REST API with unlimited calls
Bulk CSV import, up to 500 rows per file
13 store connectors included

The assistant is included

The in-app assistant drafts a label from a pasted order or email for you to confirm. It is part of the product, not an add-on.

Web, every planTelegram, Pro

API on every plan

GET /api/v1/shipments

200 OK · plan: free

Unlimited calls. The same wallet as the dashboard.

Bring last month's shipments

Put real parcels through the side-by-side quotes and compare against what those labels cost you on

ShippoPirate ShipShipStation
No contractNo card for FreeFour carriers
USPSUPSFedExDHL

Label prices are quoted live from USPS, UPS, FedEx, and DHL and shown as one number, the same number that leaves your wallet. Other vendors' plans move, so compare against their current pricing page. Full pricing details

Shipping software RFP: FAQ

Does GoatLabels support SSO or role-based access?
No. GoatLabels does not offer SSO, and it has no sub-accounts or per-client balances. If your security review requires single sign-on, mark that requirement as not met.
Does GoatLabels offer an SLA?
No. GoatLabels does not offer a contractual SLA or a dedicated account manager. Support is by email and an in-app assistant, with no phone line.
Can we use our own carrier accounts and negotiated rates?
No. Labels are bought from one GoatLabels account covering USPS, UPS, FedEx, and DHL, rate-shopped on every parcel with one all-in number per carrier. Your own carrier accounts and negotiated rates cannot be added.
Does GoatLabels cover LTL or freight in an RFP?
No. GoatLabels is parcel only and does not quote, book, or document LTL or freight. If your RFP covers pallets, score that area with a separate freight tool.
What does GoatLabels cost on a shipping software RFP price sheet?
Free is $0 a month with 50 shipments a month. Pro is $40 a month flat with unlimited shipments and cheaper label rates. The API and CSV import are on both plans, labels are paid from a prepaid wallet, and there is no contract.
Can I talk to someone about our RFP first?
Yes. Email contact@goatlabels.io with your requirements list or RFP document, your monthly parcel volume, and your origin sites. We answer each line as met or not met, price sample parcels across USPS, UPS, FedEx, and DHL, and show the API and the ledger. There is nothing to sign.

Related reading: B2B shipping software, enterprise shipping software, multi-carrier shipping software, shipping software without an annual contract, the shipping API comparison.

B2B shipping operations guides: Multi-carrier shipping software, Shipping cost allocation, Shipping rate shopping software, Sample shipping software, ShipStation alternative for B2B.

Score it on real parcels.

A requirements checklist you can reuse.
Straight answers on fit.

Copy the vendor questions into your RFP, then test GoatLabels against them on the Free plan. Free is $0 a month with 50 shipments; Pro is $40 flat with unlimited shipments.

No contract. No card for the Free plan.