Integrate Twingle Shop #69
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
from
3f64c30
to
16d6c0c
Compare
|
Rebased on PR #71 |
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
from
2779daf
to
c3eddba
Compare
Closed
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
from
c3eddba
to
8de145a
Compare
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
2 times, most recently
from
c57cd39
to
a1b17cf
Compare
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
8 times, most recently
from
0a0df6a
to
1e60b37
Compare
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
5 times, most recently
from
6b09af8
to
afea6f1
Compare
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
2 times, most recently
from
c7e2616
to
c29b658
Compare
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
4 times, most recently
from
7d2d98f
to
771479d
Compare
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
from
771479d
to
4c9235c
Compare
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
2 times, most recently
from
40008d0
to
5c24793
Compare
|
Now that all the dependencies have been merged into |
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
from
1823425
to
f2ce095
Compare
Done! 💪 But before you create an |
MarcMichalsky
force-pushed
the
integrate_twingle_shop
branch
from
d64dcb2
to
6dcc7bb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to integrate Twingle Shop orders with CiviCRM.
Objective
The objective of this Twingle Shop integration is not to blow up CiviCRM into a full-grown merchandise management system. For this reason I decided to not create a separate entity for shop orders.
On the other hand, orders should not only be attached to contributions as custom fields or notes, as this is not useful for optimizing order processes in my opinion. A workflow that also maps invoicing, status and shipping in CiviCRM after an order would be extremely inconvenient this way.
Therefore, I came to the conclusion that a viable solution is to map orders as contributions with line items and shops as price sets. This way, orders that do not arrive via the Twingle Shop, but e.g. by phone or mail, can be processed with the same workflow.
In order to match the created Twingle Shops with the existing price sets in CiviCRM, I want to use the Twingle API. Unlike in this extension, the communication is not from Twingle to CiviCRM but the other way round: CiviCRM retrieves the existing shops and products from Twingle and creates the corresponding price sets in its database.
Furthermore, the Twingle Shop integration will be completely optional, so that the behavior of this extension will not change in any way for users who do not use the Twingle Shop.
Tasks
This PR is work in progress!