diff --git a/README.md b/README.md index 5d918e9..799dacd 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,27 @@ -![BitBag](https://bitbag.pl/static/bitbag-logo.png) +

+ + + +
+ + + + + + + + + + + + + + + +

-# BitBag ShippingExportPlugin [![Build Status](https://travis-ci.org/BitBagCommerce/SyliusShippingExportPlugin.svg?branch=master)](https://travis-ci.org/bitbag-commerce/shipping-export-plugin) [![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/bitbag-commerce/shipping-export-plugin/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/bitbag-commerce/shipping-export-plugin/?branch=master) +# BitBag SyliusShippingExportPlugin ## Overview Managing shipments in any eCommerce app is something that may be tricky. There are many shipping providers and every of them has probably its own API format which allows to provide shipment data and book a courier. To make this process more straight forward and generic, we decided to create an abstract layer for Sylius platform based applications which allows you to write just simple API call and configuration form for specific shipping provider. The workflow is quite simple - configure proper data that's needed to export a shipment, like access key or pickup hour, book a courier for an order with one click and get shipping label file if any was received from the API. The implementation limits to write a shipping provider gateway configuration form, one event listener and webservice access layer.