Create BOPIS order failed with new Square application (but same Square account)

Questions
1

Hi Square team.

Issue Summary:
We are experiencing failures when calling the CreateOrder API for (BOPIS) fulfillments for this merchant. The merchant was previously good, and they recently reauthorized via OAuth with a new Square Application ID. Both the old and new applications belong to the same Square account.

Key Question: Does switching the Application ID for an existing merchant affect BOPIS functionality or require specific re-configuration on the Square Dashboard for the new App ID? If not, can you help to check it?

Technical Details:

API Endpoint: POST /v2/orders

Summary:

Application ID

sq0idp-u9qgflnAkWkBl_JmY4mmBg

Merchant ID

MLQK2Z0SM7BVK

Trace ID

CDN-22563e4a-ddce-4ca6-a104-930ed4fcbf61

API

Orders

Endpoint name

CreateOrder

Status

400

Path

POST /v2/orders

Error code

INVALID_VALUE

Square version

2023-05-17

User agent

Go-http-client/2.0

Timestamp

2026-02-12 11:31:45 GMT-6

Request

{
“order”: {
“discounts”: ,
“fulfillments”: [
{
“pickup_details”: {
“note”: “”,
“pickup_at”: “2026-02-12T17:41:44Z”,
“placed_at”: “2026-02-12T17:31:44Z”,
“recipient”: {
“display_name”: " GGG",
“phone_number”: “+15555555555”
},
“schedule_type”: “ASAP”
},
“state”: “PROPOSED”,
“type”: “PICKUP”
}
],
“line_items”: [
{
“applied_discounts”: ,
“applied_taxes”: ,
“base_price_money”: {
“amount”: 0,
“currency”: “USD”
},
“metadata”: {},
“modifiers”: [
{
“base_price_money”: {
“amount”: 7999,
“currency”: “USD”
},
“name”: “test_willimas_repeatable1”,
“quantity”: “1”,
“uid”: “ec63e43a-1827-4918-bb9d-dbe793e4db72”
},
{
“base_price_money”: {
“amount”: 198,
“currency”: “USD”
},
“name”: “test_willimas_repeatable2”,
“quantity”: “1”,
“uid”: “65872e3a-8d10-4db7-be49-9ed8987306f3”
},
{
“base_price_money”: {
“amount”: 222,
“currency”: “USD”
},
“name”: “Sausage”,
“quantity”: “1”,
“uid”: “e2179db3-cfa4-4d3b-b3a4-c19486d3e366”
},
{
“base_price_money”: {
“amount”: 666,
“currency”: “USD”
},
“name”: “Chicken”,
“quantity”: “1”,
“uid”: “27daa538-4981-46c0-a7a1-9b60c157a5a3”
}
],
“name”: “奶茶”,
“note”: “”,
“quantity”: “1”,
“uid”: “30bc377d-476b-4374-b17d-38b3f6080006”,
“variation_name”: “1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890”
}
],
“location_id”: “LS43N12AP1X0N”,
“metadata”: {},
“service_charges”: [
{
“amount_money”: {
“amount”: 10,
“currency”: “USD”
},
“applied_taxes”: ,
“calculation_phase”: “SUBTOTAL_PHASE”,
“metadata”: {},
“name”: “surcharge”,
“uid”: “ef8fcbf7-8037-4ebb-b63a-1c0949b668c1”
}
],
“source”: {
“name”: “INFI Kiosk”
},
“state”: “OPEN”,
“taxes”: ,
“ticket_name”: “”
}
}

Response Logs:

{
“errors”: [
{
“code”: “INVALID_VALUE”,
“detail”: “Do not provide a value for placed_at when creating an order.”,
“field”: “order.fulfillments[0].pickup_details.placed_at”,
“category”: “INVALID_REQUEST_ERROR”
}
]
}

2

The error your getting is for adding a placed_at value. If you remove the placed_at does the order work? :slight_smile:

3

That works, but we were trying to use the BOPIS feature.

4

Has the application been approved to use BOPIS? :slight_smile:

5

Not sure, that’s why I posted the topic here, can you please help to check it?