--- title: "Configuring your company's event types" description: "Every time a courier picks up a package, heads out for delivery, or reports they" url: https://sistrack.com/en/docs/orders/configurar-tipos-evento/ category: orders section: docs updated: 2026-08-13 --- *Markdown version for agents. This page on the web: https://sistrack.com/en/docs/orders/configurar-tipos-evento/* # Configuring your company's event types ## Introduction Every time a courier picks up a package, heads out for delivery, or reports they couldn't deliver it, the system logs an **event**. Events are the history of what happened to the shipment, and they're different from **statuses**: statuses say *where* the package is, events say *what was done*. From **System → Shipment Statuses → Event Types** you can adjust how each one works for your operation: what it's called, whether your couriers can apply it to several orders at once, and what evidence it requires. > 💡 **Changes reach the app without updating it.** Your couriers don't need > to install anything: after signing out and back in they'll see the new > configuration. Without signing out it can take up to an hour. --- ## What you can change Go to **System → Shipment Statuses** and choose the **Event Types** tab. The list appears grouped by the shipment phase where each one usually happens: pre-shipment, first mile, trunk transit, last mile, and the closing events. Tap the pencil on any event to open its configuration. ### The name Give it the name your team uses. If at your company "Picked up" is called *"Retrieved from warehouse"*, write it that way and that's what the courier will read in their app — and also what your customer sees on the tracking page. If you leave the field empty, it goes back to the default name. ### Available for batch update Enable the event so it can be applied to **many orders at once from the web panel**. Useful when something happened to a whole group: a truck arriving, a shipment held at customs. ### Offer it to couriers in the app Same thing, but on the courier's phone. It's kept separate on purpose: there are events that make sense for an office operator but not for someone delivering on the street, like warehouse or customs steps. By default your couriers have the four everyday ones: picked up, out for delivery, failed pickup, and delivery attempt. If your operation needs more, enable them here. > This switch depends on the previous one. If an event isn't available for > batches, it also can't be offered in the app. ### Visible in tracking Decide whether the recipient sees that step on the public tracking page. Turn it off for internal movements that don't add anything for whoever is waiting for the package. ### Required fields Mark what the app asks the courier for before letting them log the event: a photo, a signature, the name of who received it, a reason. **This is where it's most worth thinking it through.** If you uncheck photo and signature on "Successful delivery," your couriers will be able to close out deliveries in batches, much faster — but without individual proof of each one. The screen warns you about this before saving. It's your call: some operations value speed more, others don't. --- ## The most common case: closing deliveries in batches If your operation delivers many packages at the same place (an office building, a campus, a store), closing them one by one is slow. 1. Go to **Event Types** and find **Successful delivery**. 2. Turn on *Available for batch update*. 3. Turn on *Offer it to couriers in the app*. 4. Under **Required fields**, uncheck photo and signature. 5. Save. The next time your courier opens the app, they'll be able to scan several packages and close them together. Before doing so, the app asks for confirmation and tells them how many orders it's about to close, because that action can't be undone from the phone. ### Cash-on-delivery orders are left out If any order in the batch has cash on delivery, **the system sets it aside** and reports it separately. The rest of the batch is processed normally. This isn't configurable, and the reason is concrete: a batch shares the same data across all its orders, so it would log the same amount collected on every one of them. If three customers paid 300, 850, and 120, all three would end up with the same amount and your settlement wouldn't add up, with nothing to explain why. Those orders need to be delivered one by one, capturing what was actually collected. --- ## Frequently Asked Questions ### Why did I enable an event and the order's status doesn't change? This is expected if your flow doesn't have a stage for that event. For example: you enable *Held at customs*, the courier logs it, and the order list still shows the same status. The event **was still saved** — it's in the order's history and in tracking. What didn't change is the status, because your flow doesn't have a customs stage to put it in. If you also want it to move the status, create that stage under [Shipment Statuses](/en/docs/organization/guia-estados-de-envio/) and choose the shipment moment it corresponds to there. ### Why doesn't my courier see any events in the batch update? If the screen shows the message *"No events are available for your couriers"*, contact support: your account needs a pending update. It's not something you can fix from this screen, and enabling events manually doesn't solve it. ### Can I create new event types? Not for now. You can adjust the existing ones, which cover a shipment's full cycle. Creating a new one requires the app to know how to log it, so it's a development task, not a configuration one. ### I changed something and my courier still sees the old version. What do I do? Ask them to sign out of the app and sign back in. The app keeps the configuration for an hour so it can work without a signal; signing back in updates it instantly. ### Who can access this screen? The same people who manage shipment statuses. If you can edit a status, you can configure event types. All changes are logged with who made them and when. --- ## Related - [Customizing the status flow](/en/docs/orders/personalizar-flujo-estados/) - [Logging events on an order](/en/docs/orders/registrar-eventos/) - [Shipment Statuses Guide](/en/docs/organization/guia-estados-de-envio/)