E-commerce
July 1, 2026
"The delivery driver came on Saturday, nobody at the reception." "Parcel delivered to the office but the mail service never handed it to me." "I forgot to put the company name, the security guard refused the parcel." Three tickets where a poorly managed corporate delivery generates parcels blocked at reception, returns to sender, and office POD disputes.
The e-commerce business address delivery support covers reception hours, driver instructions, company name on the label, internal mail service, and parcels not handed to the recipient. Distinct from address change #183: here, business office delivery constraints reception hours mail service.
This guide #645 covers policy BIZDEL-SUP, flows BD-1 to BD-8, and the BIZDEL-MAP matrix. Customer service pair of the future BIZDEL bot (#646).
Summary
Why does B2B delivery generate support tickets?
The customer orders to the office. They do not specify reception hours, forget the company name, or are unaware that the building is closed on weekends. The delivery driver attempts delivery outside these hours, drops it off at reception without a named hand-off, and the package disappears in the mail service. Without an SOP, the agent confuses a residential DNR with a package held at a company reception.
Five typical office delivery friction points
Outside reception hours: delivery driver arrives Saturday or before 8 AM while the office is closed
Missing instructions: floor, building, or entry code not provided
Missing company name: security guard or reception refuses the package
Package held in mailroom: delivered to reception, but the employee never receives it
Disputed reception POD: guard's signature, but the customer denies receipt
Chronopost and Colissimo deliver to businesses subject to operating hours and recipient identification (Chronopost, pro 2026). Without BIZDEL-MAP, agents improvise instructions and POD escalation.
BIZDEL #645 vs change of address #183, DNR #509, Saturday #643 and B2B guide
Five contents, five distinct delivery address layers.
Quick matrix
#645 BIZDEL: office reception hours mail instructions constraints
Address change #183: modify street postal code post-order distinct reception constraints
DNR delivered absent #509: dispute home POD distinct office mail
Saturday #643: premium Saturday distinct office closed weekend
#646 BIZDELbot: bot tier 1 pre-purchase instructions handoff
#183 = change the address. #645 = deliver correctly to an already entered office address.
Which biz_del_* typologies should be classified?
Eight scenarios for business delivery tickets.
Eight biz_del typologies
biz_del_reception_hours: office delivery reception hours
biz_del_instructions: add delivery notes floor door-code
biz_del_company_name: company name missing or incorrect on label
biz_del_security_desk: package held by guard security reception
biz_del_mailroom: internal mail service delivery delay
biz_del_not_received_office: delivered to office but customer did not receive
biz_del_closed_weekend: delivery attempt office closed Saturday Sunday
biz_del_switch_home: switch delivery from office to home
Tags: biz_del, business_delivery, office_address. BIZDEL-MAP-GROUNDED: hours instructions from map only.
How do you structure the BIZDEL-MAP matrix?
The BIZDEL-MAP matrix documents each business delivery rule for agents and future bot #646.
BIZDEL-MAP Columns
bizdel_program_id: professional delivery checkout identifier
carrier_business_map: Colissimo Chronopost pro rules map
reception_hours_default: Mon-Fri reception hours map, e.g., 9am-6pm
weekend_office_closed: Y/N no Saturday Sunday delivery map
company_name_required: Y/N company name mandatory map
delivery_instructions_fields: checkout floor building fields map
security_desk_policy: reception drop-off authorized Y/N map
mailroom_routing_days: internal mail delay D+0 D+1 map
not_received_office_sla: wait before escalation hours map
customer_copy_checkout: pro address text map
Sync checkout company fields instructions, WMS export courier notes, helpdesk macros.
BIZDEL-SUP Policy in six rules
Six rules support corporate delivery.
BIZDEL-MAP-GROUNDED: hours instructions company from map only
INSTRUCTIONS-CITE-ONLY: delivery notes order metafield cite verbatim
COMPANY-NAME-REQUIRED-CITE: company_name_required map before ship confirm
ADDRESS183-REROUTE: change address → #183 distinct office instructions
WRONGNAME541-REROUTE: recipient name only → #541 WRONGNAME distinct company
POD-LOOKUP-BEFORE-DNR: Reception POD lookup before DNR dispute
Flow BIZDEL BD-1 to BD-8
Eight-step office delivery agent flow.
BD-1 Intake: biz_del_* intent + order_ref company_name instructions
BD-2 BIZDEL-MAP: weekend hours company security mailroom sla
BD-3 Order verify: shipping_address company delivery_notes metafield
BD-4 Carrier lookup: tracking POD signature reception API
BD-5 Classify: hours instructions mailroom not_received weekend switch
BD-6 Respond: macro BIZDEL grounded map instructions cite
BD-7 Execute: ops re-instructions intercept redelivery reception contact
BD-8 Close: tag biz_del_resolved pod_reception Y/N mailroom_wait
SLA: biz_del_not_received_office answered with POD-LOOKUP and mailroom_routing_days map in one interaction.
Essential BIZDEL Macros
Four macro corporate delivery agents.
BIZDEL-EXPLAIN-01
"Corporate delivery [bizdel_program_id]: [customer_copy_checkout map]. Reception desk hours [reception_hours_default map]. Company name [company_name_required map]. Checkout instructions: [delivery_instructions_fields map]. Weekend office: [weekend_office_closed map]."
BIZDEL-INSTRUCTIONS-01
"Order [order_ref]: driver notes [delivery_notes metafield cite]. [If unfulfilled: modification possible before shipping #183 sync ops.] Required fields: company floor building contact reception map."
BIZDEL-RECEPTION-01
"Parcel delivered [date API]: [POD signature reception cite]. Reception desk drop-off authorized: [security_desk_policy map]. Internal mail: delivery delay [mailroom_routing_days map] business days. Contact [company_name map] reception before escalation."
BIZDEL-NOTRECEIVED-01
"Carrier status [delivered reception map]. POD [signature photo cite]. Wait [not_received_office_sla map] hrs for internal mail. If absent: contact reception then escalate carrier claim map. Distinct from home DNR #509."
Edge cases: B2B pro, office closed on Saturday, multi-parcel, and remote work
Five cases outside the standard office macro.
B2B wholesale account: B2B guide separate delivery contract DTC office
Saturday office closed: #643 SATDEL weekend_office_closed reroute
Switch to home: biz_del_switch_home → #183 if unfulfilled
Multi-parcel different buildings: split instructions by line item
Teleworking mixed address: home with company name, no BIZDEL office map
Home address with optional company field ≠ BIZDEL business delivery. Check bizdel_program_id shipping method.
Essential business delivery KPIs
Five BIZDEL steering metrics.
biz_del_ticket_rate: biz_del_* tickets / pro address orders
biz_del_not_received_rate: not_received_office / office deliveries
biz_del_weekend_fail_rate: closed_weekend attempts / total office
biz_del_instructions_compliance: % complete company notes orders
biz_del_pod_accueil_rate: reception signature POD / office deliveries
Target: biz_del_instructions_compliance greater than 85% and monthly tracking of biz_del_not_received_rate.
BIZDEL anti-patterns
Five common business delivery support mistakes.
Treat as home DNR : mailroom_routing_days POD reception first
Ignore company name : COMPANY-NAME-REQUIRED-CITE map
Promise office Saturday : weekend_office_closed reroute #643
Unquoted instructions : INSTRUCTIONS-CITE-ONLY metafield verbatim
Confuse address change : ADDRESS183-REROUTE distinct reception constraints
BIZDEL with Qstomy
Qstomy on Shopify: detect biz_del intent, BIZDEL-MAP RAG grounded, instructions lookup, POD home cite, handoff #646 bot tier 1 pre-purchase.
Pipeline: #646 bot instructions hours tier 1 → #645 agents mailroom not_received escalate carrier.
Explore AI support and request a demo.
Checklist, FAQ and going further
BIZDEL Checklist (8 steps)
BIZDEL-MAP v1: schedule company instructions mailroom sla
Policy BIZDEL-SUP: 6 INSTRUCTIONS-CITE COMPANY-NAME POD-LOOKUP rules
8 biz_del_* typologies: helpdesk tags
4 BIZDEL-* macros: EXPLAIN INSTRUCTIONS RECEPTION NOTRECEIVED
Checkout pro fields: company instructions delivery_notes metafield
WMS export notes: carrier label company_name instructions sync
30 min agents training: BIZDEL vs #183 vs #509 vs mailroom
KPI Dashboard: biz_del_* section 9 instructions_compliance
FAQ
Difference with address change #183?
#183 = modify street zip code post-order. #645 = deliver correctly to office address reception constraints.
Parcel delivered to reception, not received?
BIZDEL-NOTRECEIVED-01 mailroom_routing_days POD reception before dispute.
Saturday office delivery?
weekend_office_closed map. Alternative home #183 or relay point.
Relationship with #646 bot?
#646 = bot tier 1 pre-purchase schedule instructions. #645 = agents mailroom not_received escalate.
Going further
This week: index BIZDEL-MAP pro checkout fields, audit WMS export company_name, test macro BIZDEL-NOTRECEIVED-01 agents.
Enzo
July 1, 2026
