Topic 1: I am an author, when will I be paid my royalties?
Information 1: Our authors should contact our royalties department at royalties@springerpub.com. Per our author contracts, royalty checks will be mailed towards the end of April into the first weeks of May.
Topic 2: How can disabled students access alternative formats?
Information 2: Please email accessibility@springerpub.com so they can help you with your request. You MUST provide proof of purchase in your email.
Topic 3: Where is my order?
Information 3: Can you please provide your invoice or order number? This will help our representatives find your order details.
Topic 4: Can you help me find a book?
Information 4: Can you please provide me with a title and/or ISBN? This will help our representatives find details for you.
Topic 5: How do I place a bookstore order?
Information 5: We take all bookstore/retail orders via email at cs@springerpub.com.
Topic 6: How do make a return?
Information 6: Please email us at cs@springerpub.com with all your return information, order number, reason for return/refund, questions, etc. We are unable to handle these through chat.
Topic 7: Can I pay via Chat?
Information 7: We are unable to take credit card numbers and orders via chat. If you have an invoice you would like to pay via credit card, email ar@springerpub.com your invoice number. If you are trying to place an order, you can order online at https://www.springerpub.com/ (print and test/exam prep digital access) orhttps://connect.springerpub.com/home (our eBook platform)
Topic 8: How can I get help with Journal questions?
Information 8: Please contact our journal support team at pubsvc.tsp@sheridan.com.
Topic 9: How do I cancel or change an order?
Information 9: Whether you've just placed that or it's a prior order please contact us via cs@springerpub.com for detailed help.
Topic 10: How do I report your site is broken?
Information 10: Thank you for alerting us to this issue on our site. Please provide more detail, including the link if possbile. We will forward this to our developers to remedy