Glossary

What is your delivery business model?

Everything at Bponi Storeopen in new window starts with a task, a task is a single unit of work performed at a destination, and is either a pickup or a dropoff.

If you perform deliveries that originate at one pickup location, an order in your e-commerce system can be represented by a single dropoff task in Bponi Store. This approach is common for scheduled delivery models like produce, grocery, etc...

If you perform unique pickups for each order, then you will need to create two linked tasks in Bponi Store to represent the pickup and then the subsequent dropoff. This approach is common for scheduled and on-demand models like laundry and dry cleaning, restaurant, etc...

🚧 Linked Pickup & Dropoff

For businesses creating a pickup/dropoff combo, learn more in linked tasks and task dependencies.

How do I create a task?

  • A Task should always have one Destination, which can be created using an address or a set of GPS coordinates. Creating a Destination can be done separately or during task creation.

  • The Recipient field can be used if someone needs to be informed that the task has started or completed. Recipients receive SMS text notifications and can track driver statuses when properly configured in the dashboard. The recipient field can be left empty. Like Destination, it can be created separately or during task creation.

  • A Task is created and managed by a registered Administrator (either on the dashboard or via the API), and can only be started and completed by a registered Worker.

You can decide whether to use more advanced features during task creation, including:

Do you need any information sent back to your applications?

Information can be sent back to your application (ie: order management, e-commerce, customer-facing mobile apps) by utilizing Bponi Store Webhooks, where we offer more than 10 event triggers.

Do you need custom information stored in Bponi Store?

If you would like to interact with Bponi Store’s API using external identifiers (ie: order numbers, driver’s licenses etc.), or display custom structured data to Bponi Store dashboard and mobile app users, you can store custom information on many of Bponi Store’s objects using the metadata fields. Learn more about creating and storing custom data using Metadata.

How will you validate address information prior to creating tasks in Bponi Store?

It is critical that your team has accurate address information to successfully perform pickups and deliveries. Bponi Store requires a valid destination address or coordinate pair (longitude, latitude) in order to create a task.

🚧

We highly recommend validating the address information prior to sending it to Bponi Store and using a coordinate pair at task creation, ensuring tasks will always be created.

How will you validate phone numbers prior to creating Recipients?

Bponi Store utilizes Google's phone validation library to validate all phone inputs, that includes admins, workers, and recipients. In cases where you've encountered a failed request regarding an invalid phone number, it is recommended to set up a failover to capture the failed request and respond properly.

What proof-of-delivery options do you expect to use?

Bponi Store offers the following as proof-of-delivery options:

  • Signature
  • Photo(s)
  • Barcode scanning (Premium or above plans)
  • ID verification (Premium or above plans)

All of these can be set on the task level depending on your subscribed Bponi Store plan, learn more about them in Completion Requirements.

🔔 Ready to roll?

Check out our blog post on how to get your first Bponi Store task created if you are still having doubts about using the Bponi Store API!

Last Updated: 11/29/2021, 10:25:26 PM